search

Screenly / Anthias

The world's most popular open source digital signage project.
https://anthias.screenly.io
Other
2.43k stars 612 forks source link

Wifi Access Point not loading login page #1751

Open GraphicHealer opened 1 year ago

GraphicHealer commented 1 year ago

Overview of the Issue

When I setup the Anthias install, I can get to the web portal if I start it with an ethernet cable plugged in, but if I try Wi-Fi, it will generate an AP and I can connect to it, but when the captive portal loads, it says "Sorry, this page does not exist!" and I cannot use the UI to connect it to Wi-Fi.

Reproduction Steps

Steps to reproduce this issue, eg:

Environment

ealmonte32 commented 1 year ago

@vpetersson @nicomiguelino

I can confirm this. Fresh install via bash script, screen stays black, upon physically checking by using ctrl+alt+f1 and signing in, I see that the wlan0 did actually start the anthias wifi connect SSID, I was able to visit the web GUI by going to the URL http://192.168.42.1 from a device joined to the SSID which showed up (there is no /wifi though, not sure why this person is writing this or trying to go to that URL path), then I also confirmed the containers were in fact running. So basically there is an issue with the wifi-connect container showing the IP info. Also, after I restarted, at some point it showed the wifi-connect UI for like ~20 seconds, but it was showing an incorrect old IP that was previously on the interface, then wifi-connect UI went away to the old screenly background logo which I think we need to update that image.

Here is picture of logs from wifi-connect container (had to take picture since was a quick troubleshooting):

image

ealmonte32 commented 1 year ago

@gljones2001

There is currently an issue being experienced by many with this WiFi Connect, but you are typing in the wrong Portal, it is not "http://192.168.42.1/wifi", you simply go to http://192.168.42.1 without any other directories after. That should at least bring you to the web GUI to manage the Assets, etc., while connected to Anthias Wifi Connect SSID. But, since there is no ETA on this wifi connect issue fix, I can tell you a temporary workaround that worked for me, if you want to set it up with wifi, simply get to the Pi console and remove network manager by running sudo apt remove network-manager -y and then set up the wifi with sudo raspi-config and go into the System Options and Wireless LAN.

Update

Removing network-manager is also creating a lot of error logs on the wifi-connect container, thus you should also stop it:

 sudo docker stop screenly-anthias-wifi-connect-1
GraphicHealer commented 1 year ago

@ealmonte32 I figured out that wifi-connect was causing the issue, so I built an image using balena hub, and removed wifi-connect from the docker build file. That fixed the issue, and since the balena OS asks for a wifi ssid/password when you generate the image, it still connects to wifi where I need it to.