Domoticz

Open source Home Automation System
https://forum.domoticz.com/

Stuck in login screen

https://forum.domoticz.com/viewtopic.php?t=42440

Page 1 of 1

Stuck in login screen

Posted: Tuesday 18 June 2024 18:26
by K3vin
I can't seem to login to Domoticz anymore and have trouble figuring out what is going wrong?
  • When I log in with the right credentials, the login page just reloads;
  • When I log in with incorrect credentials, I get shown an 'invalid user/ password' notice;
  • I checked the user via -nowwwpwd option and all seemed ok;
  • I followed documentation to check database integrity; I found no issues;
  • I followed the general 'troubleshooting' documentation, didn't make a difference;
  • I tried updating to the latest version, didn't make a difference;
  • Domoticz has been running for a while, before I had no issues logging in;
  • I have tried 2 different browsers; same results;
I do notice that the browser complains that the connection is not secure.

On startup I see this error:

Code: Select all

Error: WebServer(SSL) startup failed on address 0.0.0.0 with port: 443: bind: Permission denied [system:13 at /usr/local/include/boost/asio/detail/reactive_socket_service.hpp:161 in function 'bind']
I have bypassed this by adding an SSL exception in the browser, could this be causing my issue?
I can't remember if I always accessed Domoticz via https or used http before.

Any ideas what to check next?

Re: Stuck in login screen

Posted: Tuesday 18 June 2024 22:41
by waltervl
Does the Domoticz log file give any more hints, other then the SSL error?

Re: Stuck in login screen

Posted: Wednesday 19 June 2024 6:58
by gizmocuz
How did you install Domoticz?

Via docker-compose or natively via the bash command script?

first make sure no other applications are running on port 443

stop domoticz

sudo service domoticz stop

check if you can't access the web gui anymore

go to the domoticz folder and launch domoticz by hand

cd domoticz
./domoticz

Have a look at the log, first try to access the normal non-ssl page on port 8080

If you say you checked '-nowwwpwd' , you can access Domoticz without issues?

If that is the case, also go to Settings->Users and change the admin password to be sure
And in Settings->Local networks you can add your local network as well so you do not need a password
(The later is not solving this issue in a correct way, you should be able to login with a username and password)

Also try within a private browser

Make sure you have no extensions installed that blocks cookies

Re: Stuck in login screen

Posted: Wednesday 19 June 2024 20:20
by K3vin
I think I installed Domoticz via bash script (this was a few years ago).

Yes, via -nowwwpwd I can access Domoticz without issues.

Accessing Domoticz via port 8080 gives the same result.
Also an incognito session doesn't change things.

When I start Domoticz via

Code: Select all

cd domoticz
./domoticz
I actually see:

Code: Select all

Status: Login successful from xxx.xxx.xxx.xx for user 'admin'
However in the browser console I see a few json calls
http://xxx.xxx.xxx.xx:8080/json.htm?typ ... SunRiseSet
that return a 401 Unauthorized response.

Domoticz doesn't set any cookies. Should it?
As far as I can see there is nothing preventing Domoticz from setting cookies (no blocksers in Vivaldi & Firefox).

Whitelisting my local network does seem to work, so at least I now have temporary work around.

Re: Stuck in login screen

Posted: Wednesday 19 June 2024 22:16
by waltervl
McAfee antivirus plugin also can block Domoticz.

Re: Stuck in login screen

Posted: Thursday 20 June 2024 7:23
by gizmocuz
Sure, Domoticz sets cookies.
If Domoticz calls a URL it has no access to, you will see the login screen. That's perfect.
Do you block cookies?

Re: Stuck in login screen

Posted: Thursday 20 June 2024 19:47
by K3vin
No (McAfee antivirus) or cookie blocking settings or extensions in my browser(s).

I think I have found the issue though!
The time on my Rasberry pi was running behind (It was thinking it was Feb 2023).
So I guess if a cookie got set, it would have expired / be invalid to the browser.

After updating the system time I could log in again.

Thanks for the support / help!

Re: Stuck in login screen

Posted: Thursday 20 June 2024 22:03
by waltervl
There should have been a message in the Domoticz log indicating this....

Re: Stuck in login screen

Posted: Sunday 23 June 2024 10:43
by gizmocuz
This could indeed be the case as the cookie is valid for a certain time.

Re: Stuck in login screen

Posted: Wednesday 26 June 2024 8:28
by gizmocuz
Is it working correctly now?

Re: Stuck in login screen

Posted: Monday 22 July 2024 23:37
by JaLe
Hello
I see a similar issue. Can't login with admin/domoticz via the webbrowser. However it works with an old home screen bookmark on my iPhone, but not if I try to login via Safari.

The version is:
2024-07-22 23:19:12.212 Status: Domoticz V2024.4 (c)2012-2024 GizMoCuz
2024-07-22 23:19:12.212 Status: Build Hash: 731719420, Date: 2024-01-30 09:16:34

I run from a Docker container on a linux instalation and tried adding the line in the docker-compose.yml file:

environment:
- DOMOTICZ_OPTIONS=-nowwwpwd

but I continue to get the login screen where admin/domoticz is rejected (via port 8080)

I also tried to login into the container and add a resetpwd’ File, but I can't login with the default admin/domoticz

Here is the startup log:
2024-07-22 23:32:16.265 Status: Domoticz V2024.4 (c)2012-2024 GizMoCuz
2024-07-22 23:32:16.265 Status: Build Hash: 731719420, Date: 2024-01-30 09:16:34
2024-07-22 23:32:16.265 Status: Startup Path: /opt/domoticz/
2024-07-22 23:32:16.273 Sunrise: 04:58:00 SunSet: 21:31:00
2024-07-22 23:32:16.273 Day length: 16:34:00 Sun at south: 13:15:00
2024-07-22 23:32:16.273 Civil twilight start: 04:06:00 Civil twilight end: 22:23:00
2024-07-22 23:32:16.273 Nautical twilight start: 02:43:00 Nautical twilight end: 23:46:00
2024-07-22 23:32:16.273 There is no astronomical twilight in the space of 24 hours
2024-07-22 23:32:16.287 Status: PluginSystem: Started, Python version '3.9.2', 0 plugin definitions loaded.
2024-07-22 23:32:16.291 Active notification Subsystems: pushover (1/13)
2024-07-22 23:32:16.291 Status: WebServer(HTTP) startup failed on address :: with port: 8080: resolve: Host not found (authoritative) [asio.netdb:1 at /usr/local/include/boost/asio/detail/resolver_service.hpp:84 in function 'resolve'], trying ::
2024-07-22 23:32:16.291 Status: WebServer(HTTP) startup failed on address :: with port: 8080: resolve: Host not found (authoritative) [asio.netdb:1 at /usr/local/include/boost/asio/detail/resolver_service.hpp:84 in function 'resolve'], trying 0.0.0.0
2024-07-22 23:32:16.292 Status: WebServer(HTTP) started on address: 0.0.0.0 with port 8080
2024-07-22 23:32:16.295 Status: WebServer(SSL) startup failed on address :: with port: 443: resolve: Host not found (authoritative) [asio.netdb:1 at /usr/local/include/boost/asio/detail/resolver_service.hpp:84 in function 'resolve'], trying ::
2024-07-22 23:32:16.296 Status: WebServer(SSL) startup failed on address :: with port: 443: resolve: Host not found (authoritative) [asio.netdb:1 at /usr/local/include/boost/asio/detail/resolver_service.hpp:84 in function 'resolve'], trying 0.0.0.0
2024-07-22 23:32:16.297 Status: WebServer(SSL) started on address: 0.0.0.0 with port 443
2024-07-22 23:32:16.298 Starting shared server on: 0.0.0.0:6144
2024-07-22 23:32:16.299 Status: TCPServer: shared server started...
2024-07-22 23:32:16.299 Status: RxQueue: queue worker started...
2024-07-22 23:32:18.300 Status: RFXCOM: Worker started...
2024-07-22 23:32:18.300 Status: NotificationSystem: thread started...
2024-07-22 23:32:18.300 Status: EventSystem: reset all events...
2024-07-22 23:32:18.301 Status: EventSystem: reset all device statuses...
2024-07-22 23:32:18.343 Status: Python EventSystem: Initializing event module.
2024-07-22 23:32:18.344 Status: EventSystem: Started
2024-07-22 23:32:18.344 Status: EventSystem: Queue thread started...

Any help/hint is appreciated. Thanks!

Re: Stuck in login screen

Posted: Thursday 08 August 2024 18:18
by bigatis
Hello,
I have the same probleme. I reseted my browser cache and my cookies but I'm still blocked on the login page.
I tried with an other smartphone : same behavior.
I cannot access my raspberry for the moment to investigate.

NB : I m in an other time zone than my server...

Sylvain

Re: Stuck in login screen

Posted: Tuesday 26 November 2024 21:12
by paytonstsktsk
JaLe wrote: ↑Monday 22 July 2024 23:37 Hello
I see a similar issue. Can't login with admin/domoticz via the webbrowser. However it works with an old home screen bookmark on my iPhone, but not if I try to login via Safari.

The version is:
2024-07-22 23:19:12.212 Status: Domoticz V2024.4 (c)2012-2024 GizMoCuz
2024-07-22 23:19:12.212 Status: Build Hash: 731719420, Date: 2024-01-30 09:16:34

I run from a Docker container on a linux instalation and tried adding the line in the docker-compose.yml file:

environment:
- DOMOTICZ_OPTIONS=-nowwwpwd

but I continue to get the login screen where admin/domoticz is rejected (via port 8080)

I also tried to login into the container and add a resetpwd’ File, but I can't login with the default admin/domoticz

Here is the startup log:
2024-07-22 23:32:16.265 Status: Domoticz V2024.4 (c)2012-2024 GizMoCuz
2024-07-22 23:32:16.265 Status: Build Hash: 731719420, Date: 2024-01-30 09:16:34
2024-07-22 23:32:16.265 Status: Startup Path: /opt/domoticz/
2024-07-22 23:32:16.273 Sunrise: 04:58:00 SunSet: 21:31:00
2024-07-22 23:32:16.273 Day length: 16:34:00 Sun at south: 13:15:00
2024-07-22 23:32:16.273 Civil twilight start: 04:06:00 Civil twilight end: 22:23:00
2024-07-22 23:32:16.273 Nautical twilight start: 02:43:00 Nautical twilight end: 23:46:00
2024-07-22 23:32:16.273 There is no astronomical twilight in the space of 24 hours
2024-07-22 23:32:16.287 Status: PluginSystem: Started, Python version '3.9.2', 0 plugin definitions loaded.
2024-07-22 23:32:16.291 Active notification Subsystems: pushover (1/13)
2024-07-22 23:32:16.291 Status: WebServer(HTTP) startup failed on address :: with port: 8080: resolve: Host not found (authoritative) [asio.netdb:1 at /usr/local/include/boost/asio/detail/resolver_service.hpp:84 in function 'resolve'], trying ::
2024-07-22 23:32:16.291 Status: WebServer(HTTP) startup failed on address :: with port: 8080: resolve: Host not found (authoritative) [asio.netdb:1 at /usr/local/include/boost/asio/detail/resolver_service.hpp:84 in function 'resolve'], trying 0.0.0.0
2024-07-22 23:32:16.292 Status: WebServer(HTTP) started on address: 0.0.0.0 with port 8080
2024-07-22 23:32:16.295 Status: WebServer(SSL) startup failed on address :: with port: 443: resolve: Host not found (authoritative) [asio.netdb:1 at /usr/local/include/boost/asio/detail/resolver_service.hpp:84 in function 'resolve'], trying ::
2024-07-22 23:32:16.296 Status: WebServer(SSL) startup failed on address :: with port: 443: resolve: Host not found (authoritative) [asio.netdb:1 at /usr/local/include/boost/asio/detail/resolver_service.hpp:84 in function 'resolve'], trying 0.0.0.0
2024-07-22 23:32:16.297 Status: WebServer(SSL) started on address: 0.0.0.0 with port 443
2024-07-22 23:32:16.298 Starting shared server on: 0.0.0.0:6144
2024-07-22 23:32:16.299 Status: TCPServer: shared server started...
2024-07-22 23:32:16.299 Status: RxQueue: queue worker started...
2024-07-22 23:32:18.300 Status: RFXCOM: Worker started...
2024-07-22 23:32:18.300 Status: NotificationSystem: thread started...
2024-07-22 23:32:18.300 Status: EventSystem: reset all events...
2024-07-22 23:32:18.301 Status: EventSystem: reset all device statuses...
2024-07-22 23:32:18.343 Status: Python EventSystem: Initializing event module.
2024-07-22 23:32:18.344 Status: EventSystem: Started
2024-07-22 23:32:18.344 Status: EventSystem: Queue thread started...

Any help/hint is appreciated. Thanks!
It could be related to changes in Domoticz password handling or Docker configurations
1. Disable password protection: Confirm the -nowwwpwd option is correctly applied in the Docker setup:

Code: Select all

environment:
  - DOMOTICZ_OPTIONS=-nowwwpwd
After making changes, restart the container with:

Code: Select all

docker-compose down && docker-compose up -d
2 Manually reset password:
Inside the container create a resetpwd file in Domoticz's working directory:

Code: Select all

touch /opt/domoticz/resetpwd
Then restart the container. Upon startup the default credentials (admin/domoticz) should work again. Make sure to delete the resetpwd file after use for security
3. Network Configuration:
Your logs show HTTP/HTTPS binding errors. Confirm the Docker network configuration allows proper binding. Check the Docker ports section in your docker-compose.yml:

Code: Select all

ports:
  - "8080:8080"
  - "443:443"
3. Domoticz Update: Verify you're on the latest version of Domoticz. Older builds might have bugs that prevent proper login. Check for updates and re-pull the image:

Code: Select all

docker pull domoticz/domoticz
If that doesnt help maybe share additional log details
All times are UTC+02:00
Page 1 of 1

Powered by phpBB® Forum Software © phpBB Limited