Domoticz

The -www 0 might be the guilty one.
Try 8080 or another. Or otherwise make 443 something that's higher than 1024. For instance 1443, at your choice.

JakubAnderwald wrote: ↑Sunday 26 April 2020 14:30 I my service configuration file I can see the following

Code: Select all

DAEMON=/home/pi/domoticz/$NAME
DAEMON_ARGS="-daemon"
#DAEMON_ARGS="$DAEMON_ARGS -daemonname $NAME -pidfile $PIDFILE"
DAEMON_ARGS="$DAEMON_ARGS -www 0"
DAEMON_ARGS="$DAEMON_ARGS -sslwww 443"
#DAEMON_ARGS="$DAEMON_ARGS -log /tmp/domoticz.txt"
#DAEMON_ARGS="$DAEMON_ARGS -syslog"

I've changed it to the below settings, stopped domoticz, reloaded daemons with systemctl, started domoticz and verified that it now responds on port 1443.
I'm not getting the previous error anymore in the logs. Now I get the below one And I don't know if it helped connecting to myDomoticz as the website itself is down currently. Oh, Friday the 13th

As of last night, MyDomoticz has been migrated to a new host.
The current my.domoticz.com requests are being proxied by the old host, until Gizmocuz updates the DNS name.
The vanity names already work directly to the new host.
The current client code doesn't seem to detect dead connections very well. So a domoticz restart may be required in order to connect again.

== Rene

Is that my.domoticz.com server overloaded the last week? I can hardly connect to it to log on. I want it to try it out but this evening I cannot even get my instance loaded.

The server is not overloaded. But check your Domoticz log files. Feedback is welcome.

waltervl wrote: ↑Monday 01 February 2021 23:38 Is that my.domoticz.com server overloaded the last week? I can hardly connect to it to log on. I want it to try it out but this evening I cannot even get my instance loaded.

I run Domoticz beta V2020.2 (build 12901), Linux , Ubuntu 20.04 LTS
And now after succeeding to logon and load my site through MyDomoticz I have a crash of Domoticz (already 2 times this evening):
No authentication, user accounts etc. I only changed the name of the site.

It's a Domoticz issue. We will have to see on which side we can resolve this.

waltervl wrote: ↑Tuesday 02 February 2021 0:14 I run Domoticz beta V2020.2 (build 12901), Linux , Ubuntu 20.04 LTS
And now after succeeding to logon and load my site through MyDomoticz I have a crash of Domoticz (already 2 times this evening):
No authentication, user accounts etc. I only changed the name of the site.
[/code]

chimit wrote: ↑Tuesday 02 February 2021 0:18 It's a Domoticz issue. We will have to see on which side we can resolve this.

How can I help?

I also notice that from my mobile phone (with firefox) and an old edge browser on my windows laptop and firefox on my Ubuntu machine the site is not or bad responding. On Chromium, Chrome login is working. So perhaps that is also why Domoticz is crashing, bad response?

But now I see that my domoticz instance is offline since 23:59:31 hrs
Domoticz is functional, can be reached from local lan. Nothing to see in log files. For what should i search?
Instance ID is filled in in Domoticz Settings

After a reboot of Domoticz it is available again in MyDomoticz.
Loading of my instance is very slow (but I do not know what is normal ), it takes approx 1 minute to show my dashboard. Or server times out....

As I can't seem to find a suitable MyDomoticz forum, please allow me to latch on to this thread with a similar (same??) problem, discovered on 25 January 2021.

Remote access to my Domoticz system via MyDomoticz (my.domoticz.com) stopped working on Monday 25 January 2021. Until that point all worked fine. And yes - my Domoticz system can be accessed locally without any problems.

No changes have been made to my installation since October 2020, at which point my Raspberry Pi 3+ was updated with all software (Raspbian and Domoticz). Fixed IP address remains unchanged (verified on 31 January 2021).

I can log in at the my.domoticz.com login page. But the icon to access my instance is red and hence I can't get any further.

I automatically reboot my Raspberry Pi once a week (complete with Domoticz startup) and automatically do a further restart of Domoticz twice a week to minimize chances of red icon issues (of which I had quite a few in the past).

After reboot or Domoticz restart, the instance access icon in MyDomoticz is green - which I take to mean that MyDomoticz "sees" my system. But when clicking on the icon, nothing happens. There is a long wait time - and then nothing. When refreshing or using the back button, the instance access icon has become red. And that's where it all stops.

I restarted my modem / router twice on 31 January and also restarted the Pi & Domoticz at least 5 times. Despite all this, I still cannot get access to the Domoticz dashboard via MyDomoticz. I end up waiting - and then the red icon.

It seems to me that there might still be something that is not entirely completed / correct after the migration.

Let me reiterate that the local instance of Domoticz works fine and that the static IP address remains unchanged.

Anyone who could check into this so that it will again be possible to reach my instance via MyDomoticz?

Sigve

Yesterday I had another crash of Domoticz and had to reboot. Also now my instance is offline according mydomoticz while it is not. So something is wrong.
Also mydomoticz only works in Chrome browser and most of the times I try I have no dashboard visible.

So something seems wrong... I tried mydomoticz because I wanted to update the Wiki and to check the issue of @SigveM.

How can I help to troubleshoot? Can I switch on extra debug logging for MyDomoticz?

@waltervl: I see this topic is now considered solved (judging by the green tick mark next to the topic). Are you now able to access your Domoticz via MyDomoticz? If not - maybe a new thread should be opened.

I ask you because I am long-term away from where my Domoticz is installed and don't dare try to access it remotely as I am concerned that a faulty MyDomoticz may cause the local instance to freeze (it has done so in the past).

I think this Github MyDomoticz issue is the same issue we have: https://github.com/domoticz/mydomoticz/issues/9

The issue reported on Github is similar - and yet it seems to be different as it refers to the use of dynamic IP at the router level. But behind the router it seems that both our setups and the one reported on Github are identical, i.e. with static IP.

My system has static IP, permanently assigned in the router (and also enforced through command in the Pi every time it starts up or reboots). I am furthermore on a LAN, so no potential issues with WAN.

So there are similarities, but not quite the same issue, I believe. But I could be wrong.

Can anybody in this forum successfully and fully access their Domoticz instance via MyDomoticz at this point in time (5 February 2021)?

Could the cause of the MyDomoticz issue (i.e. not being able to access my instance via MyDomoticz) simply be related to the login validation?

Here's why I suspect that to be the case:

My Raspberry Pi reboots at a specific time every Monday (complete with Domoticz startup). It did so again yesterday, Monday 9 Feb 2021.

An hour or so before the automatic reboot, I logged in to MyDomoticz - and was (as expected since I had already tried to access my instance a few days earlier) presented with the red instance access icon.

A short while after the automatic reboot I again logged in to MyDomoticz. I was then - as expected as the system had just started up - presented with the green instance access icon at the MyDomoticz Dashboard.

And this is where it becomes important, I think - it clearly states for how long the system has been online. Which tells me that MyDomoticz recognizes my local instance. So there does not seem to be any kind of communication issue.

When I then click on the green instance access icon it does it's usual thing, i.e. nothing. And after that it's only a red icon.

Based on these observations - and the way it fails at the last step - I am tempted to suspect e.g. a corrupt authorization database or errors in the calls to it.

Can anyone check this / comment on it?

Until the issue is fully resolved, is there any way we could have the old version / installation of MyDomoticz back as everything worked perfectly prior to the migration in January 2021?

Dear forum members,

I am new on this forum and would like to ask you about mydomoticz. Please let me know if I should submit my reply to another topic.

A couple days ago I registered for mydomoticz. I am experiencing difficulties in connecting to the mydomoticz website. It takes long to load the login page. After logging in I tried to contact my domoticz instance. Sometimes the instances crashes or seems to be offline. Anyways, yesterday and the day before yesterday I successfully connected to my instance via mydomoticz.

What does concern me is the following oberservation: the incoming ip address is every now and then different from my external ip address and changing. I was not aware of this until checking the log file of my instance yesterday morning. Then checking the ip address shown on the mydomoticz website yesterday evening shows sometimes my external ip address and sometime a different external ip address. What is going on?

Update: Two factor code was enabled

Let me shine a light on the last few posts.

The MyDomoticz hosting has been changed and MyDomoticz now runs behind a reverse proxy.
This can explain the differences in up addresses shown

Also we are looking further into the slow/crash issues.

Finally: The SMTP settings were not entered correctly. So if meanwhile one created an account, you ask again for the registration link under "forgot" password.

chimit wrote: ↑Saturday 08 May 2021 18:43 Let me shine a light on the last few posts.

Also we are looking further into the slow/crash issues.

Thank you for reacting, any idea what is going on here?
Anything we can do to help?

chimit wrote: ↑Saturday 08 May 2021 18:43 Let me shine a light on the last few posts.

The MyDomoticz hosting has been changed and MyDomoticz now runs behind a reverse proxy.
This can explain the differences in up addresses shown

Also we are looking further into the slow/crash issues.

Finally: The SMTP settings were not entered correctly. So if meanwhile one created an account, you ask again for the registration link under "forgot" password.

What does this mean for us normal users? Do we need to make changes to our MyDomoticz settings? If so - which / how?

Or is MyDomoticz still a work in progress, meaning we should not make use of it until you / somebody says it is again functioning as it should?

waltervl wrote: ↑Sunday 09 May 2021 0:14

chimit wrote: ↑Saturday 08 May 2021 18:43 Let me shine a light on the last few posts.

Also we are looking further into the slow/crash issues.

Thank you for reacting, any idea what is going on here?
Anything we can do to help?

Just tried it and instantly Domoticz crashed:
Crashlog

Spoiler: show

Thread 10 (Thread 0x7feb36ffd700 (LWP 2871)):
#0 0x00007feb40d89dff in __GI___wait4 (pid=143956, stat_loc=0x7feb36ffb924, options=0, usage=0x0) at ../sysdeps/unix/sysv/linux/wait4.c:27
#1 0x0000561c4de9e077 in dumpstack_gdb(bool) ()
#2 0x0000561c4de9e65e in signal_handler(int, siginfo_t*, void*) ()
#3 <signal handler called>
#4 raise (sig=<optimized out>) at ../sysdeps/unix/sysv/linux/raise.c:50
#5 <signal handler called>
#6 0x0000561c4e2f22bb in http::server::CProxyClient::OnData(unsigned char const*, unsigned long) ()
#7 0x0000561c4dfe394d in ASyncTCP::cb_read_done(boost::system::error_code const&, unsigned long) ()
#8 0x0000561c4dfe3dfe in boost::asio::ssl::detail::io_op<boost::asio::basic_stream_socket<boost::asio::ip::tcp, boost::asio::execution::any_executor<boost::asio::execution::context_as_t<boost::asio::execution_context&>, boost::asio::execution::detail::blocking::never_t<0>, boost::asio::execution::prefer_only<boost::asio::execution::detail::blocking::possibly_t<0> >, boost::asio::execution::prefer_only<boost::asio::execution::detail::outstanding_work::tracked_t<0> >, boost::asio::execution::prefer_only<boost::asio::execution::detail::outstanding_work::untracked_t<0> >, boost::asio::execution::prefer_only<boost::asio::execution::detail::relationship::fork_t<0> >, boost::asio::execution::prefer_only<boost::asio::execution::detail::relationship::continuation_t<0> > > >, boost::asio::ssl::detail::read_op<boost::asio::mutable_buffers_1>, ASyncTCP::do_read_start()::{lambda(auto:1&&, auto:2)#1}>::operator()(boost::system::error_code, unsigned long, int) ()
#9 0x0000561c4dfe54a3 in boost::asio::detail::reactive_socket_recv_op<boost::asio::mutable_buffers_1, boost::asio::ssl::detail::io_op<boost::asio::basic_stream_socket<boost::asio::ip::tcp, boost::asio::execution::any_executor<boost::asio::execution::context_as_t<boost::asio::execution_context&>, boost::asio::execution::detail::blocking::never_t<0>, boost::asio::execution::prefer_only<boost::asio::execution::detail::blocking::possibly_t<0> >, boost::asio::execution::prefer_only<boost::asio::execution::detail::outstanding_work::tracked_t<0> >, boost::asio::execution::prefer_only<boost::asio::execution::detail::outstanding_work::untracked_t<0> >, boost::asio::execution::prefer_only<boost::asio::execution::detail::relationship::fork_t<0> >, boost::asio::execution::prefer_only<boost::asio::execution::detail::relationship::continuation_t<0> > > >, boost::asio::ssl::detail::read_op<boost::asio::mutable_buffers_1>, ASyncTCP::do_read_start()::{lambda(auto:1&&, auto:2)#1}>, boost::asio::execution::any_executor<boost::asio::execution::context_as_t<boost::asio::execution_context&>, boost::asio::execution::detail::blocking::never_t<0>, boost::asio::execution::prefer_only<boost::asio::execution::detail::blocking::possibly_t<0> >, boost::asio::execution::prefer_only<boost::asio::execution::detail::outstanding_work::tracked_t<0> >, boost::asio::execution::prefer_only<boost::asio::execution::detail::outstanding_work::untracked_t<0> >, boost::asio::execution::prefer_only<boost::asio::execution::detail::relationship::fork_t<0> >, boost::asio::execution::prefer_only<boost::asio::execution::detail::relationship::continuation_t<0> > > >::do_complete(void*, boost::asio::detail::scheduler_operation*, boost::system::error_code const&, unsigned long) ()
#10 0x0000561c4dfd8fb6 in boost::asio::detail::epoll_reactor::descriptor_state::do_complete(void*, boost::asio::detail::scheduler_operation*, boost::system::error_code const&, unsigned long) ()
#11 0x0000561c4dfd89d8 in boost::asio::detail::scheduler::run(boost::system::error_code&) ()
#12 0x0000561c4dfe0db0 in std::thread::_State_impl<std::thread::_Invoker<std::tuple<ASyncTCP::connect(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, unsigned short)::{lambda()#1}> > >::_M_run() ()
#13 0x0000561c4e5d518f in execute_native_thread_routine ()
#14 0x00007feb4101d609 in start_thread (arg=<optimized out>) at pthread_create.c:477
#15 0x00007feb40dc6293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Domoticz log

Spoiler: show

2021-05-09 18:24:54.069 Status: PROXY: Incoming connection from: 2a00:7c80:6:2::15
2021-05-09 18:25:07.188 Status: Incoming connection from: 2a00:7c80:6:2::15
2021-05-09 18:25:13.893 Error: Domoticz(pid:2862, tid:2871('domoticz')) received fatal signal 11 (Segmentation fault)
2021-05-09 18:25:13.893 Error: siginfo address=0xb2e, address=0x7feb410292ab
2021-05-09 18:25:16.430 Error: Thread 10 (Thread 0x7feb36ffd700 (LWP 2871)):
2021-05-09 18:25:16.431 Error: #0 0x00007feb40d89dff in __GI___wait4 (pid=143956, stat_loc=0x7feb36ffb924, options=0, usage=0x0) at ../sysdeps/unix/sysv/linux/wait4.c:27
2021-05-09 18:25:16.431 Error: #1 0x0000561c4de9e077 in dumpstack_gdb(bool) ()
2021-05-09 18:25:16.431 Error: #2 0x0000561c4de9e65e in signal_handler(int, siginfo_t*, void*) ()
2021-05-09 18:25:16.431 Error: #3 <signal handler called>
2021-05-09 18:25:16.431 Error: #4 raise (sig=<optimized out>) at ../sysdeps/unix/sysv/linux/raise.c:50
2021-05-09 18:25:16.431 Error: #5 <signal handler called>
2021-05-09 18:25:16.431 Error: #6 0x0000561c4e2f22bb in http::server::CProxyClient::OnData(unsigned char const*, unsigned long) ()
2021-05-09 18:25:16.431 Error: #7 0x0000561c4dfe394d in ASyncTCP::cb_read_done(boost::system::error_code const&, unsigned long) ()
2021-05-09 18:25:16.432 Error: #8 0x0000561c4dfe3dfe in boost::asio::ssl::detail::io_op<boost::asio::basic_stream_socket<boost::asio::ip::tcp, boost::asio::execution::any_executor<boost::asio::execution::context_as_t<boost::asio::execution_context&>, boost::asio::execution::detail::blocking::never_t<0>, boost::asio::execution::prefer_only<boost::asio::execution::detail::blocking::possibly_t<0> >, boost::asio::execution::prefer_only<boost::asio::execution::detail::outstanding_work::tracked_t<0> >, boost::asio::execution::prefer_only<boost::asio::execution::detail::outstanding_work::untracked_t<0> >, boost::asio::execution::prefer_only<boost::asio::execution::detail::relationship::fork_t<0> >, boost::asio::execution::prefer_only<boost::asio::execution::detail::relationship::continuation_t<0> > > >, boost::asio::ssl::detail::read_op<boost::asio::mutable_buffers_1>, ASyncTCP::do_read_start()::{lambda(auto:1&&, auto:2)#1}>::operator()(boost::system::error_code, unsigned long, int) ()
2021-05-09 18:25:16.436 Error: #9 0x0000561c4dfe54a3 in boost::asio::detail::reactive_socket_recv_op<boost::asio::mutable_buffers_1, boost::asio::ssl::detail::io_op<boost::asio::basic_stream_socket<boost::asio::ip::tcp, boost::asio::execution::any_executor<boost::asio::execution::context_as_t<boost::asio::execution_context&>, boost::asio::execution::detail::blocking::never_t<0>, boost::asio::execution::prefer_only<boost::asio::execution::detail::blocking::possibly_t<0> >, boost::asio::execution::prefer_only<boost::asio::execution::detail::outstanding_work::tracked_t<0> >, boost::asio::execution::prefer_only<boost::asio::execution::detail::outstanding_work::untracked_t<0> >, boost::asio::execution::prefer_only<boost::asio::execution::detail::relationship::fork_t<0> >, boost::asio::execution::prefer_only<boost::asio::execution::detail::relationship::continuation_t<0> > > >, boost::asio::ssl::detail::read_op<boost::asio::mutable_buffers_1>, ASyncTCP::do_read_start()::{lambda(auto:1&&, auto:2)#1}>, boost::asio::execution::any_executor<boost::asio::execution::context_as_t<boost::asio::execution_context&>, boost::asio::execution::detail::blocking::never_t<0>, boost::asio::execution::prefer_only<boost::asio::execution::detail::blocking::possibly_t<0> >, boost::asio::execution::prefer_only<boost::asio::execution::detail::outstanding_work::tracked_t<0> >, boost::asio::execution::prefer_only<boost::asio::execution::detail::outstanding_work::untracked_t<0> >, boost::asio::execution::prefer_only<boost::asio::execution::detail::relationship::fork_t<0> >, boost::asio::execution::prefer_only<boost::asio::execution::detail::relationship::continuation_t<0> > > >::do_complete(void*, boost::asio::detail::scheduler_operation*, boost::system::error_code const&, unsigned long) ()
2021-05-09 18:25:16.437 Error: #10 0x0000561c4dfd8fb6 in boost::asio::detail::epoll_reactor::descriptor_state::do_complete(void*, boost::asio::detail::scheduler_operation*, boost::system::error_code const&, unsigned long) ()
2021-05-09 18:25:16.437 Error: #11 0x0000561c4dfd89d8 in boost::asio::detail::scheduler::run(boost::system::error_code&) ()
2021-05-09 18:25:16.437 Error: #12 0x0000561c4dfe0db0 in std::thread::_State_impl<std::thread::_Invoker<std::tuple<ASyncTCP::connect(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, unsigned short)::{lambda()#1}> > >::_M_run() ()
2021-05-09 18:25:16.437 Error: #13 0x0000561c4e5d518f in execute_native_thread_routine ()
2021-05-09 18:25:16.437 Error: #14 0x00007feb4101d609 in start_thread (arg=<optimized out>) at pthread_create.c:477
2021-05-09 18:25:16.437 Error: #15 0x00007feb40dc6293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

The incoming connection from MyDomoticz is a v6 IP, perhaps that is an issue?