Node02.myqtthub.com timeout from my home network


#1

Hi, as the title.
I can’t access the node02 portal (it worked fine since months), with my mobile carrier instead I can. The problem is that all my devices are connected to my home network.
Any idea how I could try to solve this?

Edit:
I’ve also tried directly via IP 185.195.98.58 but same thing i receive connection timed out


#2

Hello,

Please, send connection IP where you are getting those timeouts to support@myqtthub.com so we can review your case let you know. Use:

https://asplhosting.com/ip

Best Regards,


#3

This one is not working 87.4.21.127
This one is with my mobile carrier 37.160.42.92

Here is my traceroute

ubuntu@ubuntu:~$ traceroute node02.myqtthub.com
traceroute to node02.myqtthub.com (185.195.98.58), 30 hops max, 60 byte packets
 1  fritz.box (192.168.1.1)  1.964 ms  3.189 ms  3.132 ms
 2  * * *
 3  172.17.192.54 (172.17.192.54)  13.610 ms 172.17.192.58 (172.17.192.58)  13.498 ms 172.17.192.54 (172.17.192.54)  13.435 ms
 4  172.17.192.86 (172.17.192.86)  15.282 ms 172.17.192.92 (172.17.192.92)  15.233 ms  15.186 ms
 5  172.19.184.40 (172.19.184.40)  25.052 ms  26.008 ms 172.19.184.44 (172.19.184.44)  25.961 ms
 6  172.19.177.18 (172.19.177.18)  25.916 ms  17.175 ms  16.879 ms
 7  195.22.192.144 (195.22.192.144)  16.804 ms 195.22.205.98 (195.22.205.98)  18.833 ms  22.674 ms
 8  195.22.196.69 (195.22.196.69)  23.973 ms 195.22.196.71 (195.22.196.71)  24.877 ms  27.050 ms
 9  ae-5.edge1.Milan1.Level3.net (4.68.73.37)  23.834 ms  20.349 ms  19.382 ms
10  ae2.3202.edge1.Madrid1.level3.net (4.69.140.6)  42.524 ms  42.470 ms  48.662 ms
11  213.249.106.10 (213.249.106.10)  43.128 ms aspl.demarc.cogentco.com (149.14.241.234)  38.240 ms  34.413 ms
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *

#4

Hello,

We have been reviewing your case, we have found that ip (87.4.21.127), had too many login and connection failures.

Please, review your devices’ configuration to avoid creating new connections in a fast manner when a failure (login or similar) is found, introducing a pause between retry (about 15 seconds should be reasonable).

After you have everything corrected, let us know to remove restriction.

Also, consider upgrading your Open Hub to a plan with subscription: that way you can receive reports about blocked ips that might be associated to hubs creating connection errors or order behaviours not allowed.

Automated blocking does not generates internal notification for us to review in case it is found they are associated to MyQttHub Open Plans.

Best Regards,


#5

Did you recently change SSL certificate?
I had 5 devices not working so i guess that was the issue of the retry.
Currently they are set to 5 seconds, i might increment them to 30s as well.
I’ll have to update the certificate on each of the device so i’ll let you know soon when done (hopefully in few hours)


#6

@alejandro.mayo could you please renable my ip?
I still have 1 outdated device but i will fix it as soon as i verify that the current changes are ok

Regards,


#7

Hello,

Just confirm we changed certificate provider as some users were experiencing problems
connecting using TLS.

About that, why do you have to update certificates? Are you possibly implementing certificate verification through signature or something like this?

It it is not the case, you shouldn’t have to change anything as the trust chain should apply as it happens with regular https:// connections…

Ok, about the issue, let us know when you have those devices updates to remove restriction.

Best Regards,


#8

@alejandro.mayo
yeah, currently im verifying via CA root certificate (for the science).
In any case i’ve updated them, you can proceed to remove restrictions so that i can test whether it works or not


#9

Hello,

We have removed ip blocking. You should be able to connect.

Best Regards,