Error when access API from Godaddy

I have…

I’m submitting a…

  • [ ] Bug report
    System.AggregateException: One or more errors occurred. —> System.Net.Http.HttpRequestException: An error occurred while sending the request. —> System.Net.WebException: Unable to connect to the remote server —> System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond XX.XX.XX.XX:443
    at System.Net.Sockets.Socket.InternalEndConnect(IAsyncResult asyncResult)
    at System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult)
    at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)
    — End of inner exception stack trace —

  • [ ] Performance issue
    Squidex API - unable to acess

  • [ ] Documentation issue or request

Current behavior

Expected behavior

Minimal reproduction of the problem

Environment

App Name:

  • [ ] Self hosted with docker
  • [ .] Self hosted with IIS
  • [ ] Self hosted with other version
  • [ ] Cloud version

Version: [VERSION]

Browser:

  • [ ] Chrome (desktop)
  • [ ] Chrome (Android)
  • [ ] Chrome (iOS)
  • [ ] Firefox
  • [ ] Safari (desktop)
  • [ ] Safari (iOS)
  • [ ] IE
  • [ ] Edge

Others:
Hi Squidex team,

We are currently on the Basic plan of Squidex cloud.For some reason, our website application in Godaddy is not getting any response back from Squidex API. Please see the error log below.

2023-04-09 18:13:09,050 [8] ERROR MonitoringLogger - Error while generate token
System.AggregateException: One or more errors occurred. —> System.Net.Http.HttpRequestException: An error occurred while sending the request. —> System.Net.WebException: Unable to connect to the remote server —> System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 104.26.8.32:443
at System.Net.Sockets.Socket.InternalEndConnect(IAsyncResult asyncResult)
at System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult)
at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)

Our Godaddy IP address is 160.153.155.190.

Please let us know.

I have not blocked anything. Can you try to make a ping?

I believe you are using Cloudflare for cloud.squidex.io. The IP address 104.26.8.32:443 seems to be with Cloudflare. Would you be able to check 160.153.155.190 is in blacklist of cloudflare firewall maybe?

There is nothing in the firewall logs. Can you make a request to Google.com. Sometimes it is not possible to make any outgoing requests

Without Squidex API Calling - Our website is functioning properly.

but if we proceed with Squidex API calling - the website does not work…also the Squidex content does not populate.

till yesterday it was working fine , suddenly it stopped working.

Please help in investigating further.

Hi Sebastian, Can you please help on this.

The IP address 104.26.8.32:443 seems to be with Cloudflare. Would you be able to check 160.153.155.190 is in blacklist of cloudflare firewall maybe?

Hello @Sebastian,

Our website is on a shared hosting on Godaddy. Our hypothesis is that the IP address of the shared hosting at Godaddy is getting blocked by the firewall of Cloudflare which cloud.squidex.io uses. We are creating a ping function to check if we are able to get the pings through to Google as well as 104.26.8.32:443

This has been a blocker for us since we are not able to consume the API from Squidex cloud. It used to work fine a few days back but we started noticing the timeout around Sunday.

System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 104.26.8.32:443

Will keep you posted once we have the Ping logs.

Thanks
Sujith

@Sebastian We are able to ping 104.26.8.32 (squidex ip) from locally , but not able to ping (getting FALSE) from Go daddy

and for google.com, we are able to ping.

we think you should allow (Go Daddy.com) traffic.

Hi @Sebastian

The IP 104.26.8.32 pings false. google.com pings true. Please see screenshots.

This is a blocker as our customer facing website is down because of this API timeout / blocking issue. Please help us resolve this issue asap.

Thanks
Sujith

@Sebastian

I am confident that Cloudflare is blocking the requests from our hosted website at Godaddy with IP 160.153.155.190. I tried pining a few of our other websites which uses Cloudflare and those returns false as well.

Please suggest.

Thanks
Sujith

Hello @Sebastian

I pinged 104.26.8.32 and cloud.squidex.io from a VPS we have on digital ocean and the ping returns true. Please see log below.

IP 104.26.8.32

root@ubuntu-s-1vcpu-1gb-sgp1-01:~# ping -c 5 104.26.8.32
PING 104.26.8.32 (104.26.8.32) 56(84) bytes of data.
64 bytes from 104.26.8.32: icmp_seq=1 ttl=57 time=1.54 ms
64 bytes from 104.26.8.32: icmp_seq=2 ttl=57 time=0.982 ms
64 bytes from 104.26.8.32: icmp_seq=3 ttl=57 time=1.01 ms
64 bytes from 104.26.8.32: icmp_seq=4 ttl=57 time=1.01 ms
64 bytes from 104.26.8.32: icmp_seq=5 ttl=57 time=1.01 ms

— 104.26.8.32 ping statistics —
5 packets transmitted, 5 received, 0% packet loss, time 4005ms
rtt min/avg/max/mdev = 0.982/1.108/1.537/0.214 ms

cloud.squidex.io

root@ubuntu-s-1vcpu-1gb-sgp1-01:~# ping -c 5 cloud.squidex.io
PING cloud.squidex.io(2606:4700:20::ac43:47fb (2606:4700:20::ac43:47fb)) 56 data bytes
64 bytes from 2606:4700:20::ac43:47fb (2606:4700:20::ac43:47fb): icmp_seq=1 ttl=57 time=1.82 ms
64 bytes from 2606:4700:20::ac43:47fb (2606:4700:20::ac43:47fb): icmp_seq=2 ttl=57 time=1.55 ms
64 bytes from 2606:4700:20::ac43:47fb (2606:4700:20::ac43:47fb): icmp_seq=3 ttl=57 time=1.40 ms
64 bytes from 2606:4700:20::ac43:47fb (2606:4700:20::ac43:47fb): icmp_seq=4 ttl=57 time=1.42 ms
64 bytes from 2606:4700:20::ac43:47fb (2606:4700:20::ac43:47fb): icmp_seq=5 ttl=57 time=1.40 ms

cloud.squidex.io ping statistics —
5 packets transmitted, 5 received, 0% packet loss, time 4006ms
rtt min/avg/max/mdev = 1.400/1.516/1.816/0.159 ms

This confirms that our IP address 160.153.155.190 at Godaddy is getting blocked. Please let us know.

Thanks
Sujith

But this means that the block is not at the domain level, right? I am not sure what I can do. I can talk with cloudflare support, but this might take a while. Often the ongoing ip is shared between multiple accounts so the block might not even your fault

@Sebastian please escalate it to your provider and allow the same.

I have created a rule that skips all checks

please see response - where iam getting (True) response on Squidex Community version.

on otherhand the paid version - still iam unable to get response.

(post withdrawn by author, will be automatically deleted in 24 hours unless flagged)

Iam 100 % confident now, that it is getting blocked from Squidex side.

@Sebastian please help here.

It’s 48 hrs now, still struggling for resolution

pls. help

Regards,
Siddhesh Sawant
+91 9664555399

As I said:

  1. There is not a single firewall rule in cloudflare (except the one I just created).
  2. There is not a single firewall rule everywhere else on our side.

I have created a custom rule, that is skipping all protection:

But there is not a single request logged at cloudflare for this IP. So I am not sure if the network calls even arrive at cloudflare:

Hello @Sebastian

We are getting a dedicated IP for our hosting at Godaddy. Hopefully, the new IP will be clean and not in the blacklist of Cloudflare.

Don’t you have dedicated support plan? Please let me know.

Thanks
Sujith

@Sebastian

We have raised a query on Cloudflare support.
https://community.cloudflare.com/t/cloudflare-block-godaddy-shared-ip/496152

Godaddy takes around 24 hours to assign the dedicated IP address and they have not assigned it yet.

Thanks