MyDomoticz revisited Topic is solved

[chimit]

Hi!

Is it possible for you to look up a line number in proxyclient.cpp with addr2line -e /path/to/domoticz 0x0000561c4e2f22bb

== Rene

Let me shine a light on the last few posts.

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

[waltervl]

Hi!

Is it possible for you to look up a line number in proxyclient.cpp with addr2line -e /path/to/domoticz 0x0000561c4e2f22bb

== Rene

Let me shine a light on the last few posts.

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

I am not sure what you are asking but i did this:

Code: Select all

udoox86@UDOO-x86:~$ addr2line -e /home/udoox86/domoticz/domoticz 0x0000561c4e2f22bb
??:0
udoox86@UDOO-x86:~$ sudo addr2line -e /home/udoox86/domoticz/domoticz 0x0000561c4e2f22bb
[sudo] password for udoox86: 
??:0

[Abeltje]

Dear Rene,

Thanks for your reply.

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

I was afraid that the connections between the MyDomoticz server and my local Domoticz instance were tampered with.
So the following incoming connections were from the proxy server:

_{2021-04-04 09:55:28.597 Status: PROXY: Incoming connection from: 52.213.26.200
2021-04-04 10:10:51.217 Status: PROXY: Incoming connection from: 52.213.77.15
2021-04-04 10:18:18.408 Status: PROXY: Incoming connection from: 83.26.69.237
2021-04-04 10:19:48.013 Status: PROXY: Incoming connection from: 52.213.77.134}

and were not compromised?

BR,

Abeltje

[McJohn]

Raspberry with Domoticz 2020 version + 4G router

Just made a new mydomoticz account.

It takes long (very loooong, a couple of minutes) to load the Domoticz Home page (tried different browsers), and also the other Domoticz pages.
So this is not workable.
(and beside this the load of the https://my.domoticz.com login page is also very very sloooow)
(From a well working fiber 1000mb connection)
When the connection finally is established, it works also very slow and after closing the window of the browser en make a re-connection, the MyDomotics login-doll is red...

Edit: After the red doll appears , in the internal network Domoticz was also not reachable anymore (Domoticz Offline message in browser). VNC connection was working well and at the RPI Browser Domoticz was running normal. After a restart of Domoticz (via the menu) it was still not reachable, only with a restart of the whole RPI, Domoticz was running normal again in the internal network .


This problem has been around for a few months, still no solution?

Kind regards,

John

[McJohn]

PS: my.domoticz.com is still unreachable.

Will there be a solution? Or has this project died a silent death?

[chimit]

It should be reachable, even since your last post.
We will continue fixing bugs, as soon as our free time allows.

PS: my.domoticz.com is still unreachable.

Will there be a solution? Or has this project died a silent death?

[McJohn]

Thanks for your quick reply, I appreciate that.

This morning we have tested the link (https://my.domoticz.com) from another internet connection (other company location) and there it isn't also not reachable.

John

[chimit]

Thanks for your quick reply, I appreciate that.

This morning we have tested the link (https://my.domoticz.com) from another internet connection (other company location) and there it isn't also not reachable.

John

Weird, when I click on the link you gave, it works for me with 2 other people logged in and 700 instances connected.

[McJohn]

It's very unstable.
5 minutes ago suddenly it worked but now it's again not reachable.

[chimit]

It's very unstable.
5 minutes ago suddenly it worked but now it's again not reachable.

Most of the connections are "up" constantly, for more than a day in a row, without disconnecting.

[McJohn]

Most of the connections are "up" constantly, for more than a day in a row, without disconnecting.

That's good news!
After 10 times refreshing the browsers (Safari and Chrome) and 30 minutes waiting, suddenly the connection to my.domoticz.com is working now.
(the blue "log off" button gives in Safari a "dead" connection)

OK, that was problem 1.

Do you have also a solution for problem 2?
(The very slloooooow (couple of minutes) build up of the Domoticz dashboard, connection to a Domoticz RPI Server connected at a 4G router).

[SigveM]

All is not well, I'm afraid. As a matter of fact - nothing works for me. Nor has it worked since around mid January.

I too see that there's around 700 systems connected and 2 - 5 people logged in.

I can log in. And I get the green icon up. But clicking on the green icon results in one thing only - nothing (except a hanging page and a red icon when getting back to my login page).

Refreshing, waiting - been there, done that. Too many times. And it still does not work.

I check roughly every 2nd day as my system automatically restarts 3 times a week. And I can tell from MyDomoticz page that is has restarted as the icon is green when logging in. But beyond that - nothing. Click on the icon and I keep running in the same non-productive circle.

So clearly some issues with MyDomoticz still, I'm afraid.

[waltervl]

It is still not working for me too.
Just tried again. I could get logged in after I rebooted my Domoticz system (Proxys instance was offline -Red- according MyDomoticz from 22-may)
After login I could connect to my system but after 1 minute it crashed (as usual).

crash log of thread:

Spoiler: show

Thread 10 (Thread 0x7f30952ee700 (LWP 1555)):
#0 0x00007f309adf9dff in __GI___wait4 (pid=2331, stat_loc=0x7f30952ec9a4, options=0, usage=0x0) at ../sysdeps/unix/sysv/linux/wait4.c:27
#1 0x0000557ab1687077 in dumpstack_gdb(bool) ()
#2 0x0000557ab168765e 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 0x0000557ab1adb2bb in http::server::CProxyClient::OnData(unsigned char const*, unsigned long) ()
#7 0x0000557ab17cc94d in ASyncTCP::cb_read_done(boost::system::error_code const&, unsigned long) ()
#8 0x0000557ab17ccdfe 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 0x0000557ab17ce4a3 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 0x0000557ab17c19d8 in boost::asio::detail::scheduler::run(boost::system::error_code&) ()
#11 0x0000557ab17c9db0 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() ()
#12 0x0000557ab1dbe18f in execute_native_thread_routine ()
#13 0x00007f309b08d609 in start_thread (arg=<optimized out>) at pthread_create.c:477
#14 0x00007f309ae36293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

[McJohn]

The idea of this solution is brilliant, specially when the IP address of the Domoticz server changed regularly.
So, the base is good and for us it's not a problem to pay for this solution but then it also has to work perfectly!

We discovered that the link:
https://my.domoticz.com/
Doesn't work in Safari, in Chrome that link works good.
This link:
https://my.domoticz.com/mydomoticz/dashboard
Works good in Safari and Chrome.

So, that problem is solved (with the exception of the blue logout button, that keeps the Safari window hanging).

The second problem is a more major problem.
We just test it again and the first time the login to the Domoticz Dashboard was super fast and smooth but then suddenly out of nothing the Domoticz Dashboard window is frozen and seems to be that the connection was dead.
So, we closed the window and made a reconnection with the green doll but that's soooooo slooooooow again and not workable at all.
In our case the Domoticz server keeps (luckily) running and didn't crashed this time.

How can we help to solve this problem for ones and for all?
Shall I send an IT engineer of our company to the site where the proxy server is running?

John

[Chuckleuk]

Not working for me either. Login OK, green man, but attempting to load the Domoticz pages gets a blue web page and my Raspberry Pi based domoticz crashes. It's been like this several months.

Was quite surprised to hear it's working for some people - several hundred lucky people with stable connections - when it sounded to me like this once wonderful part of domoticz had stopped working for everyone a while back and it was dead.

Seems like it devs think it's ok, but for a lot of people it's badly not working. If there's anything I can do to contribute to a wider fix I'm all ears!

Sent from my Pixel 3a using Tapatalk

[Marcjeok]

Created an account today, but have not been able to get this working. Turned the option off again in settings, because Domoticz (on my Pi) keeps crashing. After turning off this option, Domoticz seems to be stable again. Hope this will be fixed, because the idea is really good.

[McJohn]

Any updates of this problem?
What's the timeline for a solution?

[chimit]

I removed the apache2 proxy in between.
All seems to go better now. proxy.mydomoticz.com has a new ip address now.

[waltervl]

I can confirm, after entering my instance on my.domoticz.com it did not crash. I could stay working on it.
I still have the issue that Firefox (on Linux) will not log in, it will not even show the login screen. Chromium will and can log in and do my work as like home.
Sorry, while typing I get now a login screen in Firefox ( it took several minutes!!) Login then is fast.
But entering the instance (clicking on green Icon) again is really slow, taking minutes to show my dashboard. After that browsing is almost like normal.

I had to reboot Domoticz on my system in able to have my instance active (green icon in MyDomoticz) again.

[waltervl]

I can confirm, after entering my instance on my.domoticz.com it did not crash. I could stay working on it.
I still have the issue that Firefox (on Linux) will not log in, it will not even show the login screen. Chromium will and can log in and do my work as like home.
Sorry, while typing I get now a login screen in Firefox ( it took several minutes!!) Login then is fast.
But entering the instance (clicking on green Icon) again is really slow, taking minutes to show my dashboard. After that browsing is almost like normal.

I had to reboot Domoticz on my system in able to have my instance active (green icon in MyDomoticz) again.

To add, I have the same Firefox access issue on my Android phone. Chrome is working normal.