Skip Navigation

Home › Support › English Support › [Resolved] cURL error 7: Failed to connect to ate-production.s3proxy.wpml.org port 443: Connection refused

[Resolved] cURL error 7: Failed to connect to ate-production.s3proxy.wpml.org port 443: Connection refused

This thread is resolved. Here is a description of the problem and solution.

Problem:
After migrating a website and changing its URL, the client faced issues with WPML registration and visibility of translations on the frontend, despite being able to edit and save them in the backend.
Solution:
1. We recommended temporarily disabling the firewall to allow changes to be saved and to ensure connectivity with WPML services.
2. We suggested adding specific code to the theme's functions.php to test server connectivity with WPML's services:

$response = wp_remote_get('https://ate-production.s3proxy.wpml.org');<br />print_r($response);

3. To further diagnose connectivity issues, we advised using cURL to test access to external URLs, including a specific WPML URL, with the following code:

$ch = curl_init('https://ate-production.s3proxy.wpml.org');<br />curl_setopt($ch, CURLOPT_FOLLOWLOCATION, 1);<br />$data = curl_exec($ch);<br />print($data);

4. After making the main changes, the client planned to re-enable the firewall and whitelist IPs associated with the domain names, expecting them to be static.

If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, we highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If problems persist, please open a new support ticket.

This is the technical support forum for WPML - the multilingual WordPress plugin.

Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.

Tagged: 

This topic contains 6 replies, has 2 voices.

Last updated by Ilyes 10 months, 4 weeks ago.

Assisted by: Ilyes.

Author Posts
May 30, 2024 at 1:28 pm

Sytse

We developed a website on bootendart.bluntlabs.nl. It was then migrated to the live environment on bootendart.nl. After going live, WPML noted that the site had moved and asked whether it was a production or development site. Support then advised me to choose development, as production resulted in me not being able to edit the translations.
The site ran smoothly for a period of about two weeks. During that time, we were also able to edit translations. Till yesterday. Then WPML asked to re-register the site. This did not work (see also ticket https://wpml.org/forums/topic/registering-site-2/) Eventually we succeeded, but the site had to be registered under the old development url bootendart.bluntlabs.nl as bootendart.nl was not recognised.
After the 'successful' registration, we can work in the translations again, can save them and also open the saved translations again in the backend, but in the frontend we don't see the changes.
So it seems that while we can now work in the tables linked to the old development site, they are not shown/unloaded or linked to the current live site.
May 30, 2024 at 3:20 pm
May 31, 2024 at 9:44 am #15691520

Sytse

Ilyes found two possible problems:
The user https://wpml.org/forums/users/willemd-4/ (probably the previous website builder) also still had a bootendart.nl WPML registration. They unregistered it.
After that I retried to register the website under bootendart.nl, which still wasn't possible. Finally I registered it under 'bootendart.bluntlabs.nl' again, but that resulted again in the connection error.

The second problem Ilyes found, was "Ilyes : And we found an issue of key mismatch under WPML troubleshooting, the key you have is linked to the old URL"

I am confident that this issue may well be the co-cause of the whole problem. I hope you guys can find a solution in this. I await your response.
June 1, 2024 at 2:14 am #15694341

Ilyes
Supporter

Languages: English (English ) French (Français ) Arabic (العربية )

Timezone: Pacific/Easter (GMT-06:00)

Your ticket got transferred to our systems team,

It seems that there is a mismatch between your site's ID on your site and the one we have on our server,

It is currently showing the ID of your testing site (old) which could explain this issue,

I will let you know once we get a solution,
June 1, 2024 at 5:06 pm #15694938

Sytse

Thank you for the update Ilyes,
And this seems like a logical explanation for the problems we are experiencing.
I hope the ID can be corrected soon so that we can work in the website again; after re-registering it or not.
If this can be done by Monday afternoon, very much so. There is an important presentation on Tuesday, for which the website actually needs to be updated. I hope that can be done.
Thanks for your efforts!
Sytse
June 4, 2024 at 1:16 pm #15702219

Ilyes
Supporter

Languages: English (English ) French (Français ) Arabic (العربية )

Timezone: Pacific/Easter (GMT-06:00)

Hello again,

I have received multiple updates about this kind of issues,

Here are the steps you need to test first :

1- Another link to whitelist :

ate-production.s3proxy.wpml.org

2- Test connection

On your server, you can add to your theme's functions.php this code to check connectivity, It is just temporary! you should remove it after you get the result in the frontend:

$response = wp_remote_get( '<em><u>hidden link</u></em>' );
print_r($response);

3- To rule out WordPress issues, we can use the code from the last thread in StackOverflow in a separate .php file somewhere on the host.

$ch = curl_init("<em><u>hidden link</u></em>");    // initialize curl handle
curl_setopt($ch, CURLOPT_FOLLOWLOCATION, 1);
$data = curl_exec($ch);
print($data);

You can do also tests with our URL: hidden link

$ch = curl_init("<em><u>hidden link</u></em>");    // initialize curl handle
curl_setopt($ch, CURLOPT_FOLLOWLOCATION, 1);
$data = curl_exec($ch);
print($data);

And querying our URL should return something like:

MissingKeyMissing Key-Pair-Id query parameter or cookie value1

Please let me know what you found,

Best,
June 5, 2024 at 11:29 am #15706324

Sytse

Ilyes,

This time, turning off the firewall worked immediately, solving the problem immediately and allowing us to save the translations again. (This still without re-registering the site under the final domain. So we can move on again).
Once we have made the main changes, I will turn on the firewall again, whitelist the IPs behind the given domain names, expecting them to be static, and see if it continues to work. But it will be fine.

Main question I have now:
Since the site is registered under the name (and ID?) of the development environment (bootendart.bluntlabs.nl), can we uninstall this old development environment without any problem? And will the final website (bootendart.nl) continue to run under WPML without any problems?

Sytse
June 5, 2024 at 11:15 pm #15709045

Ilyes
Supporter

Languages: English (English ) French (Français ) Arabic (العربية )

Timezone: Pacific/Easter (GMT-06:00)

Hello,

To test this out without deleting your Data, you can remove your staging site by deleting the key from your WPML.org account. Please try the following:

1. Go to https://wpml.org/account/sites/
2. Click the Trash icon next to the dev site
3- Test your live site to see any issues occurred
4- If nothing got affected, then you can delete your DEV environment

Best,