September 23, 20232 yr Hello, Working on a friends system remotely who said they can no longer connect to the GUI , which i confirmed. I was able to connect via SSH with the IP address, and pull diagnostics ifconfig /boot I also performed from SSH nano /boot/config/docker.cfg and change DOCKER_ENABLED="yes" to be DOCKER_ENABLED="no" To attempt to see if it was a docker port, but that didn't seem to resolve the concern Have still been unsuccessful ... trying to figure out why webGUI is not triggering. I was curious if someone could review the attached to point me in the correct direction, if the diags show anything? Thank you in advance! tower-diagnostics-20230922-1922.zip Edited October 6, 20232 yr by bombz
September 23, 20232 yr Community Expert Did you try these ports: PORT="280" PORTSSL="2443" If the issue is with SSL you can also try disabling, change USE_SSL="yes" to "no" (/boot/config/ident.cfg) and reboot.
September 23, 20232 yr Author 3 hours ago, JorgeB said: Did you try these ports: PORT="280" PORTSSL="2443" If the issue is with SSL you can also try disabling, change USE_SSL="yes" to "no" (/boot/config/ident.cfg) and reboot. Hello, Appreciate the follow-up. I did not try those ports via the webGUI IP:PORT I will do my best to attempt these suggestions, since I am remote from the system assisting a friend, I will have them setup my remote connection back to them and see if these suggestions allow me to access the webGUI. If they do, would I be required to suggest for them to always user IP:PORT to access the webGUI moving forward, or where do you think the problem resides after investigation? Thank you. Edited September 23, 20232 yr by bombz
September 24, 20232 yr Community Expert 19 hours ago, bombz said: If they do, would I be required to suggest for them to always user IP:PORT to access the webGUI moving forward Yes, unless you change the ports back to default.
October 5, 20232 yr Author On 9/24/2023 at 4:28 AM, JorgeB said: Yes, unless you change the ports back to default. Hello, Attempted with https://IP:2443 Was able to successfully connect (invalid SSL cert). Trying to attempt to understand how to set things back to normal for this instance, so the port is no longer required? Any suggestions? Thanks.
October 5, 20232 yr Author Solution Hello, Would that be in a .cfg file somewhere on the flash drive? I am trying to understand how he got it to the state it is in. Could he have done something in docker, and revproxy that made this act up in such a way? Look forward to hearing back. Thank you for your assistance with this! EDIT: Found in Settings->Management Access Thanks Edited October 6, 20232 yr by bombz
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.