-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
curl: (7) Failed to connect to gateway-{pin}.local port 8443: Connection refused #71
Comments
Hello, I have the exact same problem. Developer mode is activated, a token has been created but when I try to access the API, I have Connection Refused. I can ping my Tahoma Box, but the 8443 port is not opened. What should I do ? Regards. |
Try it with leaving the "gateway-" part out. so:
|
Well, that this could not be the right solution you should also see above. If I try it, I will receive 'curl: (6) Could not resolve host:'. If you look above 'ping gateway-{pin}.local' will work. So leaving out the gateway part is not right. The host name can be resolved. If I use the ip address instead I will receive:
|
I do not have a Somfy box or whatever, but I've made the plugin for Domoticz based on testwork of others. They indicated that this is the way to get it to work. Although they were adding it to there hosts file (see setup instructions). |
After changing my internet router, I seem to be experiencing the same problem, even though it worked fine before. |
I too get a connection refused error when trying to access an internal API. |
@tomcomwinter I have also tried posting on the forums to see if I get any farther with this problem. I will keep you updated if I find anything. Also, It seems Somfy will perform a maintenance to update Tahoma boxes today (I have seen a message on the forum website: https://forum.somfy.fr/) |
Thanks!
I hope the box update will open the ports.
…On Tue, 11 Apr 2023 at 11:28 Coko ***@***.***> wrote:
@tomcomwinter <https://github.com/Tomcomwinter> I have also tried posting
on the forums to see if I get any father with this problem. I will keep you
updated if I find anything. Also, It seems Somfy will perform a maintenance
to update Tahoma boxes today (I have seen a message on the forum website:
https://forum.somfy.fr/)
As I live in France, this maintenance might only apply to France, not sure.
—
Reply to this email directly, view it on GitHub
<#71 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A5BGAEYLJIPLQBCBQX4PVZ3XAUIZBANCNFSM6AAAAAARRB3KPI>
.
You are receiving this because you were mentioned.Message ID:
***@***.***
com>
|
@Coko7 I encounter the same problem. I was running TaHoma box firmware fw_version=2022.7.4-11. When I launch: the result is: It seems that everything is correct and DNS is correctly resolved. I don't know what is going wrong. |
Okay, I have just updated my TaHoma box and tried again. I still can't figure out whatever is going with the hostname, but I tried the API using ip addr directly and now this works (it did not work before): And I get the following answer from the API: Did you try curl with IP instead @Eridani78 ? |
@Coko7 Thanks for your message. Before update, using the IP address was not working for me either. Your message is very usefull and bring one step further. Thanks again |
@Eridani78 Glad I could help a little. Yes, you are right, the token is unneeded for API version. Little update on my side: Now, it seems to be working when I use curl with the hostname. If it still does not work with hostname, try these different options:
In my particular case, I know that |
@Coko7 |
Just wanted to say that everything is back to normal on my side. I have no more problem connecting to the API, and my Node.js automated script that connects to my TaHoma is working again. This firmware update did solve the problem I was having in the end, and I am hoping that this very problem was fixed in the update and that it is not some weird bug that shows up from time to time. For anyone who has yet to successfully query their local gateway API, here is what you can try:
foo@bar:~$ ping 192.168.1.42 # or
foo@bar:~$ ping gateway-1111-2222-3333 # You may want to append the following suffix to your hostname: ".local" or ".home"
foo@bar:~$ curl -k "https://192.168.1.42:8443/enduser-mobile-web/1/enduserAPI/apiVersion" # using IP (did not work before but should work ever since the last update)
foo@bar:~$ curl -k "https://gateway-1111-2222-3333.local:8443/enduser-mobile-web/1/enduserAPI/apiVersion" # using hostname (Using ".local" here but you may want to try without it or with ".home" instead) I don't think port number can be changed, so make sure it is {"protocolVersion":"2023.1.4-7"} One last thing: I don't know if Somfy already does it, but it would be useful to have some kind of changelog for these firmware updates. The API itself has great capabilities, but it could benefit from some additional documentation, and again, having some kind of release notes for developers could help. |
Again, thanks a lot for your very beneficial information. I suspect a bad configuration related to SSL security or reverse proxy configuration or DNS server configuration or Firewall configuration ??? What I do not understand is when I run the following nmap command: If you perform the same operation on your network, could you please tell me if the nmap response indicates that all ports are closed or if port 8443 is available ? Thanks in advance for your help. My configuration
|
I am sad to learn that you could not fix it on your end. I have just tried nmap on my gateway and I do get open ports: foo@bar:~$ ping 192.168.1.42
Starting Nmap 7.80 ( https://nmap.org ) at 2023-04-12 17:13 CEST
Nmap scan report for gateway-1234-1234.home (192.168.1.42)
Host is up (0.0063s latency).
Not shown: 998 closed ports
PORT STATE SERVICE
443/tcp open https
8443/tcp open https-alt
Nmap done: 1 IP address (1 host up) scanned in 2.58 seconds One weird thing I have noticed is that my gateway is reachable through foo@bar:~$ ping gateway-1234-1234.home
PING gateway-1234-1234.home(gateway-1234-1234.home (00:25:96:FF:FE:12:34:56)) 56 data bytes
From pc-foobar.home (00:25:96:FF:FE:12:34:56) icmp_seq=1 Destination unreachable: Address unreachable
From pc-foobar.home (00:25:96:FF:FE:12:34:56) icmp_seq=2 Destination unreachable: Address unreachable
From pc-foobar.home (00:25:96:FF:FE:12:34:56) icmp_seq=3 Destination unreachable: Address unreachable
From pc-foobar.home (00:25:96:FF:FE:12:34:56) icmp_seq=4 Destination unreachable: Address unreachable I still think that something is wrong with how my gateway is handled by my network, but it is working despite this issue. I don't get why my gateway has a hostname missing the last 4 pin digits, but can still be reachable using the full pin. Furthermore, I do not know much about networking, so if someone experienced can explain to me how this works, please do. But back to you @Eridani78, it is weird that it does not show port 8443 or 443 as open, it should. This makes me think that this problem we are having has not been fixed by the firmware update, but instead appears randomly. It seems like sometimes ports 8443 and 443 are closed on the gateway, making its API unreachable, that's my guess. Did you try rebooting the gateway to see if anything changes? |
I tried many things including rebooting the Tahoma box but no success so far ... So, concerning nmap command, your response showing that ports 443 & 8443 are open let me very questioning ? Regarding the truncated hostname in your nmap response, it is very strange too. So the question remains for me: If somebody can help ? |
@Eridani78 This seems to be broken on my end, I haven't touched my script at all, but yesterday evening it could not access the API because the hostname did not resolve to the gateway, and today it works, but I haven't changed anything (neither in the network nor the name of my gateway) You mentioned you had a livebox 5. I have also changed mine recently, and now I have the same livebox. I have tried using Now that I think about it, when you used |
I have made some more research, and there seems to be an issue with the hyphen/dash character "-" in hostname/DNS names in the newest livebox 5. If I head over to the admin interface of my livebox and try to save the hostname of my TaHoma a bunch of times, it removes the last
It's not the same thing described in the messages on the forum, but they seem to have a similar problem, and it seems renaming their network and removing the hyphen in the name fixed it. I do have a hyphen in my network name, is it the same for you @Eridani78 ? |
Hi @Coko7 I confirm working with an Orange Livebox 5. But just for now: Regarding the DNS configuration in the Livebox, I had the same behavior as when I tried to enter '1234-1234-1234' as a hostname, it removes the last '-1234'. Finally, I let this field empty for the moment. So the last thing is when I launch:
which for me conclude that the port 8443 is definitively NOT OPEN in my TaHoma Box. |
Hi @Coko7 Here is the follow-up ... |
Great update @Eridani78! I'm still receiving the connection refused error, but it got me thinking if we're using the same device. Thanks! |
I operate the same TaHoma box. For me, this solved the issue. |
Thank you very much! I have had the exactly same issue with the closed ports resulting in a "connection refused". The reset (or better "resynchronisation") according to this video https://www.youtube.com/watch?v=CY0phXUOS8s did the trick. After having an additional restart, the resynchronisation took ~5-10min enabling a succesfull connection. Now its working with the Openhab 3.4.3 Somfy Tahoma Binding in "Developer Mode" 👍 |
Unfortunately I'm still have the issue (connection refused)
The tahoma comes back online but still with connection refused. I'm curious whether I'm missing something. Thank you |
@tomcomwinter |
Thank you @maschiach for the quick response! Thanks! |
Hi @tomcomwinter |
Hi,
Thanks for your reply! Is this fix specific to my box or is it a broader
fix that will be rolled out? Would you happen to know when we should expect
the fix?
Thank you!
…--
Tom
On 7 Jul 2023 at 12:10:14, llavorel-somfy ***@***.***> wrote:
Hi @tomcomwinter <https://github.com/Tomcomwinter>
Your product is facing a certificate issue, what is quite unexpected.
I will let you know when it is fixed.
—
Reply to this email directly, view it on GitHub
<#71 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A5BGAE3Q7PSW4UKR3YBEDWDXO7G7NANCNFSM6AAAAAARRB3KPI>
.
You are receiving this because you were mentioned.Message ID:
***@***.***
com>
|
I have the same issue with my Connexoon box running version 2023.3.4-5. I also get connection refused. Any ideas? |
Hi @tomcomwinter we have deployed new certificates. Would you be able to test again after rebooting your TaHoma ? |
My Connexoon gateway also refuses any local TCP connection. Developer mode is enabled and I am able to ping the device. Rebooting did not help. Any suggestions @llavorel-somfy ? |
Similarly to your situation, I'm unable to connect locally. I have enabled the "developer" function, but when using nmap, I get the following result: All 1000 scanned ports on 192.168.1.90 are in ignored states. With my PIN code 0805-0888-3872, I have tried your methods to connect locally, using the IP address and hostname, but to no avail. I don't understand. Could there be an issue with the Somfy box rather than my network? EDIT: |
How did you manage to do that? |
Hi @bobskee Have you succeeded to connect ? |
No, unfortunately nothing has changed. Any advice? |
Would you accept to share your gateway {pin} with me ? |
Sorry for my late reply. I think I missed the notification for it earlier. |
Forcing a firmware reset (holding the RST while powering the Connexoon) seems to have fixed my issue. Now I can connect to the local API. |
Hi,
I tried to access my local gateway but this does not work. Hope you can help me.
At first I activated the Developer made. Then I created my token using Postman. Here is the Postman Collection.
The gateway is on 192.168.0.37. I can ping it:
Then I tried nmap:
In the cloud, you will see that the developer mode is enabled. However, I don't seem to have a port running on my TaHoma box.
So I want to try to use curl:
It does not work. I also can try it without the port 8443. Same result.
I will get the error:
What can I do?
Thanks in advance.
The text was updated successfully, but these errors were encountered: