If i login via 192.168.1. x i am redirected to
http://192.168.1. x/pwa/login.html#
and below the brown p there is Phoscon-GW button shown on the same IP
if i login via nginx proxy manager by domain deconz.domain.de i am redirected to
deconz.domain. de/pwa/login.html#
BUT i only get the brown P but NO Button below to login the gateway.
Anyone any idea?
Using the latest Version btw.
I am having the same issue when I use devices on iOS(17). I just get a blank screen
It does work on Safari on MacOS
Sometimes it works for me on Chrome Desktop but most of the time it does not work. On Mobile Chrome or Firefox i could not get it to work.
As far as iOS is concerned, this problem is now fixed, using the newly arrived Phoson App. 
Thanks alot. But the app works for me, only the Webpages make the problems. Am i in the wrong thread? 
No, no, was just a thought.
Have you seen this? I’d try this update
Did this, still the same Problem, maybe another bug. Phoscon App is the only docker container that i am not able to let it open bei a domain and only by ip
Any new insights into this problem?
We did a lot of fixing regarding the login problems in the newer Android /iOS App versions
And also Phoscon browser App shiped with deCONZ > 2.25.x
+1, same problem.
@ChrisHae
I am running the deconzcommunity/deconz docker image, version 2.26.3, behind an nginx reverse proxy. If I access deconz through the FQDN, the gateway does not appear. If I map the container’s port 8080 to a host port and access deconz via the IP, the gateway does appear.
Here are the browser console outputs for each variant:
I had a short look at pwa/js/scanner.js. I don’t fully grasp what is happening there, but towards the bottom, there are regex matches against IP address ranges that look suspicious to me.
If there are specific things you would like me to try with my setup, please let me know. 
