Hi
For security reasons, I want to limit the access to the the Welcome Webhook URL.
What is the source IP range(s) used by Netatmo when calling the webhook ?
Thanks
K.
Firewall configuration for webhook
Re: Firewall configuration for webhook
Hi there,
Unfortunately, we don't provide this kind of information at the moment.
Regards,
Unfortunately, we don't provide this kind of information at the moment.
Regards,
Ismail, Netatmo Team
Re: Firewall configuration for webhook
Hi,
Since today, it seems that the WebHooks calls are now coming from a new load balanced platform or IPs range : lb3.admin.monkees.fr
It used to be b*.netatmo.net for days before.
My firewall has reject the new callers IPs and after 5 tries, the WekHooks requests have been stopped on Netatmo side.
How can I activate them again ? My "Ban Status" is still set to "NO"...
Do I have only to wait for 24h ? Do I need to drop and add the WebHook again ?
I can create another App instance, but it's not very nice.
Thank you for your answer !
Since today, it seems that the WebHooks calls are now coming from a new load balanced platform or IPs range : lb3.admin.monkees.fr
It used to be b*.netatmo.net for days before.
My firewall has reject the new callers IPs and after 5 tries, the WekHooks requests have been stopped on Netatmo side.
How can I activate them again ? My "Ban Status" is still set to "NO"...
Do I have only to wait for 24h ? Do I need to drop and add the WebHook again ?
I can create another App instance, but it's not very nice.
Thank you for your answer !
-
- Posts: 41
- Joined: 23 Nov 2016, 17:56
Re: Firewall configuration for webhook
Can someone solve this question?
My webhook always gets banned.
My webhook always gets banned.
-
- Posts: 41
- Joined: 23 Nov 2016, 17:56
Re: Firewall configuration for webhook
Or is there any way to debug the webhook?
Code: Select all
▼body:
status: "ok"
time_exec: 0.033099889755249
time_server: 1560092631
Re: Firewall configuration for webhook
Hi,
did you get this resolved? I have the same problem...
Regards
Chris
did you get this resolved? I have the same problem...
Regards
Chris
-
- Posts: 41
- Joined: 23 Nov 2016, 17:56
Re: Firewall configuration for webhook
Nope, this is the answer from Netatmo on 18-06
Dear Giel,
I have updated all this data to our backend team,
they will make sure to investigate and correct this situation quickly.
thanks a lot for your patience.
Prashanth
Technical specialist
Dear Giel,
I have updated all this data to our backend team,
they will make sure to investigate and correct this situation quickly.
thanks a lot for your patience.
Prashanth
Technical specialist
Re: Firewall configuration for webhook
Hi,
support got back to me and told me that I have to use ports 80 or 443 for the webhook. After changing my used port, webhooks work!
Cheers,
Chris
support got back to me and told me that I have to use ports 80 or 443 for the webhook. After changing my used port, webhooks work!
Cheers,
Chris
-
- Posts: 41
- Joined: 23 Nov 2016, 17:56
Re: Firewall configuration for webhook
I've seen the same, I was using another port as 443
Netatmo:
Hi Giel,
Thank you for your reply.
After investigation, we have found out the reason behind the banning.
let me first thank you for your patience during this investigation.
For security purpose, the only ports allowed are the 80 for HTTP and 443 for https.
It seems you have spécified a different port on your webhook URL,
this explains the repetitive bans.
Please change the ports to correct this situation.
Me:
Please let me use another port
It’s also worth pointing out that using a non-standard port for https connections increases security. Using port 443 is like having a house and everyone knows where the door is – but if you use a non-standard port, you are hiding the door like a needle in a haystack.
Netatmo:
Hi Giel,
I can understand your view, let me inform our devs, and get more information on why we have chosen to limit the ports.
I'll catch you back quickly.
thanks.
Netatmo:
Hi Giel,
Thank you for your reply.
After investigation, we have found out the reason behind the banning.
let me first thank you for your patience during this investigation.
For security purpose, the only ports allowed are the 80 for HTTP and 443 for https.
It seems you have spécified a different port on your webhook URL,
this explains the repetitive bans.
Please change the ports to correct this situation.
Me:
Please let me use another port
It’s also worth pointing out that using a non-standard port for https connections increases security. Using port 443 is like having a house and everyone knows where the door is – but if you use a non-standard port, you are hiding the door like a needle in a haystack.
Netatmo:
Hi Giel,
I can understand your view, let me inform our devs, and get more information on why we have chosen to limit the ports.
I'll catch you back quickly.
thanks.