Soap & cURL don't work after upgrading Ubuntu
Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
I'm running a WordPress site on an Ubuntu VPS Server.
After upgrading the server using: do-release-upgrade
it was upgraded from Ubuntu 16.04.04 to 18.04.01.
Soap and cURL don't seem to work any more, although they are still installed and were working fine before.
Any ideas how to fix this issue?
ubuntu upgrade curl vps
add a comment |Â
up vote
0
down vote
favorite
I'm running a WordPress site on an Ubuntu VPS Server.
After upgrading the server using: do-release-upgrade
it was upgraded from Ubuntu 16.04.04 to 18.04.01.
Soap and cURL don't seem to work any more, although they are still installed and were working fine before.
Any ideas how to fix this issue?
ubuntu upgrade curl vps
I would first debug the service, before trying to do a SOAP call. e.g.telnet <IP> <port>
Output should be:Trying :: <IP>
Connected to <IP>.
Escape character is '^]'.
` Another thing you can try is to read the server withnmap <IP>
to check if the ports you need to contact SOAP are open. If they are not, most likely you will need to config your firewall usingfirewal-cmd
, you can check how here: cyberciti.biz/faq/⦠HTH :)
â Kramer
Sep 28 at 12:51
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I'm running a WordPress site on an Ubuntu VPS Server.
After upgrading the server using: do-release-upgrade
it was upgraded from Ubuntu 16.04.04 to 18.04.01.
Soap and cURL don't seem to work any more, although they are still installed and were working fine before.
Any ideas how to fix this issue?
ubuntu upgrade curl vps
I'm running a WordPress site on an Ubuntu VPS Server.
After upgrading the server using: do-release-upgrade
it was upgraded from Ubuntu 16.04.04 to 18.04.01.
Soap and cURL don't seem to work any more, although they are still installed and were working fine before.
Any ideas how to fix this issue?
ubuntu upgrade curl vps
ubuntu upgrade curl vps
edited Sep 28 at 11:09
Jeff Schaller
33.6k851113
33.6k851113
asked Sep 28 at 10:32
Emre Ozpalamutcu
1
1
I would first debug the service, before trying to do a SOAP call. e.g.telnet <IP> <port>
Output should be:Trying :: <IP>
Connected to <IP>.
Escape character is '^]'.
` Another thing you can try is to read the server withnmap <IP>
to check if the ports you need to contact SOAP are open. If they are not, most likely you will need to config your firewall usingfirewal-cmd
, you can check how here: cyberciti.biz/faq/⦠HTH :)
â Kramer
Sep 28 at 12:51
add a comment |Â
I would first debug the service, before trying to do a SOAP call. e.g.telnet <IP> <port>
Output should be:Trying :: <IP>
Connected to <IP>.
Escape character is '^]'.
` Another thing you can try is to read the server withnmap <IP>
to check if the ports you need to contact SOAP are open. If they are not, most likely you will need to config your firewall usingfirewal-cmd
, you can check how here: cyberciti.biz/faq/⦠HTH :)
â Kramer
Sep 28 at 12:51
I would first debug the service, before trying to do a SOAP call. e.g.
telnet <IP> <port>
Output should be: Trying :: <IP>
Connected to <IP>.
Escape character is '^]'.
` Another thing you can try is to read the server with nmap <IP>
to check if the ports you need to contact SOAP are open. If they are not, most likely you will need to config your firewall using firewal-cmd
, you can check how here: cyberciti.biz/faq/⦠HTH :)â Kramer
Sep 28 at 12:51
I would first debug the service, before trying to do a SOAP call. e.g.
telnet <IP> <port>
Output should be: Trying :: <IP>
Connected to <IP>.
Escape character is '^]'.
` Another thing you can try is to read the server with nmap <IP>
to check if the ports you need to contact SOAP are open. If they are not, most likely you will need to config your firewall using firewal-cmd
, you can check how here: cyberciti.biz/faq/⦠HTH :)â Kramer
Sep 28 at 12:51
add a comment |Â
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f472029%2fsoap-curl-dont-work-after-upgrading-ubuntu%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
I would first debug the service, before trying to do a SOAP call. e.g.
telnet <IP> <port>
Output should be:Trying :: <IP>
Connected to <IP>.
Escape character is '^]'.
` Another thing you can try is to read the server withnmap <IP>
to check if the ports you need to contact SOAP are open. If they are not, most likely you will need to config your firewall usingfirewal-cmd
, you can check how here: cyberciti.biz/faq/⦠HTH :)â Kramer
Sep 28 at 12:51