Skip to main content

Issue with curl to specific domain after upgrading to CloudLinux

Hoxer
Since we upgraded to CloudLinux curl simply times out to a specific domain of one of our clients. I tried the command: curl -v https://google.com
and it works correctly, While if I try the client's API I get [QUOTE] curl -v * Trying 111.111.111.111... * TCP_NODELAY set * connect to 111.111.111.111 port 443 failed: Connection timed out * Failed to connect to api.example.com port 443: Connection timed out * Closing connection 0 curl: (7) Failed to connect to api.example.com port 443: Connection timed out
(domain and ip removed) On any other server it works correctly, and client claims it happens since we upgraded to CloudLinux 8.6 6 days ago (From AlmaLinux 8.6) Their IP is static and it does not show when I execute iptables -S
or in the file /etc/csf/csf.deny
The issue also occurs when CSF is off. No hits for the IP in ModSec Any ideas?

Comments

5 comments

Date Votes
  • cPRex Jurassic Moderator
    Hey there! I'm not seeing anything obvious on my end about CloudLinux and Curl. As a test, have you pulled the user out of CageFS, or at least rebuilt CageFS to see if that changes the behavior?
    0
  • Hoxer
    Hey there! I'm not seeing anything obvious on my end about CloudLinux and Curl. As a test, have you pulled the user out of CageFS, or at least rebuilt CageFS to see if that changes the behavior?

    I have tried both rebuilding and pulling the user out of CageFS Unfortunately this did not fix the issue. edit: I tried a simple curl -v api.example.com
    as root and its also not responding
    0
  • cPRex Jurassic Moderator
    Are you able to connect with any other tools, or is it specifically curl? I'm not sure there would be anything in the operating system update that would lead to this behavior, and it doesn't seem like this would be related to cPanel tools. Does a basic ping or traceroute work properly?
    0
  • Hoxer
    Are you able to connect with any other tools, or is it specifically curl? I'm not sure there would be anything in the operating system update that would lead to this behavior, and it doesn't seem like this would be related to cPanel tools. Does a basic ping or traceroute work properly?

    You are right. it's not only curl. It seems like there is no connectivity at all. I already called the API provider to see if they blocked the customer's dedicated ip but they said they did not. And I also tried from different ips on same servers and none work. API provider did confirm that the calls have stopped at the same date as we upgraded. At this point i'm not sure what else to try.
    0
  • cPRex Jurassic Moderator
    Unfortunately I don't have any ideas on my end either. It would be up to your hosting provider to do some additional network diagnostics to see if that issue can be further isolated.
    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post