DirectAdmin/Wordpress and Curl

mikewazar

Hi all

I'm having some issues with DirectAdmin hosting on MyW.pt, where I have a Wordpress site hosted I'm trying to get curl working on @risharde's Oxygen promotion

The issue:

"Hi Mike, thanks for the details! So I have an issue which I have not encountered before which is an error with curl. Curl seems not be able to load anything externally from your website setup. I'm not sure if this is a php configuration but I don't see this on any of my wordpress sites. Screenshot attached, we need to resolve this for the setup and likely for me to activate Oxygen Builder. Please let me know?"

The error:

I tried fiddling around with PHP, setting max uploads/etc but I cannot get this working and MyW.pt support is a bit sluggish and this needs to be fixed somewhat quickly.

Would anyone here know what the cause might be, and how to fix it?

I'd appreciate any direction or advice

Mike

Levi

Forum is not support board for low end provider. Reffer to providers ticketing system, phone line support, fax or mail your issues via fedex.

Generaly curl error indicates the lack of permissions. Directadmin's jailed ssh is crap at best.

mikewazar

@LTniger said:
Forum is not support board for low end provider. Reffer to providers ticketing system, phone line support, fax or mail your issues via fedex.

Generaly curl error indicates the lack of permissions. Directadmin's jailed ssh is crap at best.

I know, I did send a ticket and I'm communicating between the two providers. I just made a post in the help section in the hope that someone might know a quick fix in the meantime.

Arkas

@LTniger said: Forum is not support board for low end provider.

Take it easy buddy, he is just asking for help in case someone has had a similar experience in general.

niceboy

Dont expect quicker resolution with MyW.pt. The service will be great until you need support.

mikewazar

Yip it seems support is not really a priority. It's a set and forget service (that breaks often enough to warrant me wanting my money back at times)

jobayer

You have not written what error you're getting in your post. You need to debug the application to find out the issue first before getting any solutions. There are several ways to do it.

if you have access to server root, just ssh to console and try execute this curl -v https://google.com and post the outpur here. if you don't have access to ssh try to create a php file and visit that php file. it will display the errors (if any).

php code: https://pastebin.com/5Tu9UBB9

ElonBezos

@jobayer said:

if you have access to server root,

i bet he doesn't have.
Jailed ssh is common for a shared hosted, shouldn't expect much

mikewazar

@ElonBezos said:

@jobayer said:

if you have access to server root,

i bet he doesn't have.
Jailed ssh is common for a shared hosted, shouldn't expect much

I expect at the very least a response from @MikePT

jobayer

It's possible to check from jailed ssh (if he have properly setup and permission). However, forget the ssh he can just use the given PHP script, which will also work. Just create a PHP file, put that code in it, save it, and then open it in your browser. That's all. If there is any problem, the curl_error PHP function will display it. From my experience, in shared hosting, we usually face problems due to firewall blocks, nameserver problems, or missing PHP curl extensions. As he has not posted the error, there's no way to say what's happening there.

MikePT

@niceboy said:
Dont expect quicker resolution with MyW.pt. The service will be great until you need support.

Woo?

MikePT

@mikewazar said:
Yip it seems support is not really a priority. It's a set and forget service (that breaks often enough to warrant me wanting my money back at times)

I'm not aware of anything breaking?

MikePT

@jobayer said:
It's possible to check from jailed ssh (if he have properly setup and permission). However, forget the ssh he can just use the given PHP script, which will also work. Just create a PHP file, put that code in it, save it, and then open it in your browser. That's all. If there is any problem, the curl_error PHP function will display it. From my experience, in shared hosting, we usually face problems due to firewall blocks, nameserver problems, or missing PHP curl extensions. As he has not posted the error, there's no way to say what's happening there.

I've already replied to the ticket in question, so I could check if the remote IP is banned in our end. All accounts have SSH access, this could be debugged further via SSH certainly.

Cheers!

FatGrizzly

I too think the other webhost(?) Ip is banned on myw.pt

try unblocking the other ip via WHMCS?(if myw offers that)

mikewazar

@jobayer said:
You have not written what error you're getting in your post. You need to debug the application to find out the issue first before getting any solutions. There are several ways to do it.

if you have access to server root, just ssh to console and try execute this curl -v https://google.com and post the outpur here. if you don't have access to ssh try to create a php file and visit that php file. it will display the errors (if any).

php code: https://pastebin.com/5Tu9UBB9

Ouput of curl -v https://google.com

https://pastebin.com/LHb5bESL

Output of the PHP script: https://endgame.co.za/test.php

@MikePT @jobayer is this the expected output?

EDIT: I added http://endgame.co.za/oxygen.php which connects to oxygenbuilder.com (I think?) and that doesn't seem to be doing what the Google test script does. Perhaps this is the issue?

[endgamec@wde1 ~]$ curl -v https://oxygenbuilder.com/

• Trying 35.230.4.135...
• TCP_NODELAY set
  ^C
  [endgamec@wde1 ~]$

The connection to https://oxygenbuilder.com times out.

ahnlak

Well, curl looks to work to other destinations, so I'd guess there's a firewall block either at the host end or oxygenbuilder's end.

It's pingable from the host end (although I guess it could be a port specific block) so I'd want to check the other end.

MikePT

@mikewazar said:

@jobayer said:
You have not written what error you're getting in your post. You need to debug the application to find out the issue first before getting any solutions. There are several ways to do it.

if you have access to server root, just ssh to console and try execute this curl -v https://google.com and post the outpur here. if you don't have access to ssh try to create a php file and visit that php file. it will display the errors (if any).

php code: https://pastebin.com/5Tu9UBB9

Ouput of curl -v https://google.com

https://pastebin.com/LHb5bESL

Output of the PHP script: https://endgame.co.za/test.php

@MikePT @jobayer is this the expected output?

EDIT: I added http://endgame.co.za/oxygen.php which connects to oxygenbuilder.com (I think?) and that doesn't seem to be doing what the Google test script does. Perhaps this is the issue?

[endgamec@wde1 ~]$ curl -v https://oxygenbuilder.com/

• Trying 35.230.4.135...
• TCP_NODELAY set
  ^C
  [endgamec@wde1 ~]$

The connection to https://oxygenbuilder.com times out.

Replied.

I've whitelisted the IP, and I checked first if it was banned - it's not.

Do check the ticket, you'll likely need to ask them if they're blocking us.

mikewazar

Brilliant @ahnlak @MikePT

I have asked them

risharde

Thanks for all these checks @mikewazar and @MikePT , I've gone ahead and sent the issue to Oxygen Builder! Hopefully this is an easy fix if all goes well. I haven't encountered this before but I doubt they will provide any details on why this IP might be blocked - which will make it frustrating because it's just an unnecessary headache to have to ask them to allow IPs (which is an unknown factor in delivering these to customers such as @mikewazar).

Will keep you guys posted accordingly!

jobayer

@mikewazar said:
@jobayer is this the expected output?

Well, curl is properly working on your server thats why it's working for google.com. But it does not work for oxygenbuilder.com (35.230.4.135).

So it's a firewall game Now the question is who blocked whom. As @MikePT said its whitelisted in your server end possibly they have blocked your server ip. Try to whitelist your server ip from their end or alternatively you can use proxy to bypass the restrictions.