I have created a Self-hosted mobile administration gateway for Incus with a secure web dashboard, Android client, role-based controls, audit logging, and Docker deployment. The idea is an android mobile app that lets you view all your containers across all your incus servers and stop, start, restart and shell into them as well as see their current status.
Watch my tutorial here.
Find it here on GitHub and here on Docker Hub.
Lovely! Will give it a try soon 
Make sure that you have extra servers defined in the docker compose or use the IP address instead.
Thanks I used an IP Address, may I just try to ssh from the container?
Looks cool, can I ask - Qwen3.6? Feels very familiar UX wise when you ask Qwen to go mad on something 
It’s patterned after my other apps like Incus Dashboard, Incus Backup, Incus Forge and Blast Radius. I did use ChatGPT in development. Incus Mobile Server and the Android client represent 14,000 lines of code and 250 hours of work on my part. Contribute if you can. Thx.
I wrote LXDMosaic (before AI existed as we know it today) so 250 hours to me is low lol, but keep going! I’m not a hater just the UI/UX seem’d familar from what I know of AI
(I am aware you made a video about LXDMosaic, i really am not hating - just asking)
Agreed. I am familiar with LXDMosaic. I was a pre-cursor to LXConsole that Matthew Penning created. I felt from the beginning that we needed some type of mobile management system and so Incus Mobile was created. I am cranking out a YouTube video as we speak.
I don’t offer comparisons was just the “contribute” line that got me.
All the best! (Sorry for hijaking the thread - this does actually look cool, just was asking about Qwen specifically)
I am a real novice as compared to you regarding app development. I am an Infrastructure guy and the last time I programmed was in assembly language, Fortran and Cobol if that helps. I am rather quickly catching on to Node.js which shows you that even old guys can learn new tricks. Having AI is like owning a radial saw. Without the right skills, you just end up with a pile of scraps.
Yo, build what you need, that’s how I learnt what I did - I built what I needed (dont ask me about assembly of Fortran, I don’t have to write that because of people like you) - I don’t need praise, I dont even use modern stuff - what you built looks awesome, its what you need so go build it! (others need it to)
I’m going to stop commenting here when my curiosity gets the better, I really wasn’t 2nd guessing you - I really just wanted to know if it was “Qwen vs Something else” - sorry for getting up in your business.
So I build this tool with Android Studio and installed it on a dev phone, I installed the server behind a caddy with a TLS Cert and allowed my IP.
Problem is: I don’T see any instances because I have them all in projects and ims doesn’t seem to knew about incus projects right?
Another question, what about SSH Keys for the install of certs?
Odd that you would get a 400. Is it possible that you are using a different management port for incus other than 8443 or are you restricting management access to the target incus server based on origin?
Yes, all futures I suppose. My thoughts are that projects should work, however I did test that. I have my server behind NginX Proxy Manager and it behaves. Websockets are required.
What does connection details look like? Is the server receiving the token pairing request?
I got it running, had to add --all-projects to scottibyte-incus-mobile-server/incus.js at main · ScottiBYTE/scottibyte-incus-mobile-server · GitHub
Interesting. Let me know how you like it.
I do! It’s fun to open a shell on my phone
I submitted 2 PR’s to get it going, will think a bit about this project.
