Device registration works now (however the button to hide already added devices has no effect)
80 if you take the text as-is. Personally, I use 8080 for test containers. Line to modify:
SERVER_PORT=8080 -e
The button to hide existing devices does not hide newly added devices, so as not to disturb the visible list.
However, if you leave and come back to the page, the devices already added should have disappeared.
Thanks, Iâll take good note of that!
Have you waited long enough for everything to load? Expect at least 2-5 full minutesâŠ
Iâm up to 13 ^^
With the following in the logs
\u003e 2023-01-15T22:39:27+0100 \u003cinfo\u003e index.js:63 (Server.\u003canonymous\u003e) Server listening on port 8089
Donât make fun of my computer thatâs called Knacki!!! 
Improvement proposal
I have a suggestion @cicoub13.
At my place, as I said, I have two networks:
- The LAN, managed by my Freebox at 192.168.1.0/24, which hosts Gladys
- The WiâFi, managed by a dedicated Linksys router at 10.44.1.0/24, which hosts my phones
Obviously, on the scan, no phone is detected, since I imagine the scan uses the locally detected IP range.
Can you add a field in the settings to add an IP range to scan?
That way I can specifically declare the additional network to scan, which would be my WiâFi. That will allow detecting my phones.
On the dev side, I hope itâs simple enough, like calling the library to do the scan while specifying an IP range.
Name detection bugs
Finally, still nothing regarding hostnames on my side. Hereâs what my Freebox shows me; you can see that my desktop is detected via its DHCP name, mDNS and NetBIOS. Additionally, the manufacturer linked to the MAC address is also shown.
On Gladysâ side, my desktop is discovered, but without any names. And Gladys also scanned itself (the one on the right).
A strange thing when I run this command :
docker run -d --log-driver json-file --log-opt max-size=10m --cgroupns=host --restart=always --privileged --network=host --name gladys -e \
NODE_ENV=production -e \
SERVER_PORT=8089 -e \
TZ=Europe/Paris -e \
SQLITE_FILE_PATH=/var/lib/gladysassistant/gladys-production.db -v /var/run/docker.sock:/var/run/docker.sock -v /var/lib/gladysassistant:/var/lib/gladysassistant -v /dev:/dev -v /run/udev:/run/udev:ro \
atrovato/gladys:lan-manager
The port doesnât seem to be listening?
Can someone explain to me whatâs wrong?
Usually with docker run I publish a port to access it, here we donât publish anything « -p »
we only have an EXPOSE in the Dockerfile, right?
EXPOSE is when youâre on a bridge network; in host mode all ports are open
Is your container running?
Is your command on a single line?
Ah okay ! For the record I didnât know ^^
As for the command, yes it runs correctly with all the arguments.
You can see it here :
I donât get why I canât connect
I had this kind of issue on my laptop, couldnât connect to the container when I was on WiâFi. On Ethernet no problem â I havenât looked into it much, but I have the impression the Docker network is acting up.
Are you running it on your NAS?
Nope I run it on my WSL via Docker ^^
Iâm installing my network outlet tomorrow.
Also, Iâve never had this kind of issue with other containers personally 
Itâs still strange, Iâll let you know tomorrow, thanks again!
You need a special configuration for Windows and WSL. Iâm trying to find the tutorial for you but in any case you wonât be able to test much because WSL runs inside a VM so itâs a different network, and network discovery wonât give anything.
Edit: Apparently thereâs no need to tinker anymore â GUI app support is available now.
So you just need to install Chrome in your WSL distro and run it;
I can do it outside my WSL (I just realized that ^^')
I confirm that no device is backing up at my home.
Hello,
Iâm following up on this topic because Iâm interested in being able to have my phone detected via Wi-Fi.
Does it work?