CyberSEO - Topic: Known good proxies fail to connect

CyberSEO on Known good proxies fail to connect

Thu, 04 Sep 2025 19:39:49 +0200

We tested the proxies you sent, and they work fine here with RSS Retriever - the plugin connects and imports posts without any issues. So the proxies themselves and the plugin code are OK.

If they still fail for you, the problem is specific to your hosting environment. Many shared hosting providers block outgoing proxy connections or restrict certain ports. You'll need to check with your hosting support whether external proxies are allowed from your account.

CyberSEO on Known good proxies fail to connect

Thu, 04 Sep 2025 18:28:42 +0200

The proxy format you're using (user:pass@ip:port) is correct. If you continue to experience issues with the plugin, it is likely that your proxy provider is blocking connections from your hosting server.

Since you don't have SSH access to test this directly, the easiest solution is to email us your proxy details, including the full login and password, at Login to see this link.

davet3929 on Known good proxies fail to connect

Thu, 04 Sep 2025 18:10:51 +0200

Here are the results from the checker Login to see this link that I mentioned in my initial post, with passwords XXXd out. I can email you the passwords if you want to check yourself. Otherwise how should I proceed in debugging this?

Proxy	Status	Speed	Location	ISP	Hosting	Known Proxy
23.95.150.145:6114:taeqndzq:XXX	success	454	United States, Buffalo	HostPapa	true	true
198.23.239.134:6540:taeqndzq:XXX	success	463	United States, Buffalo	HostPapa	true	true
45.38.107.97:6014:taeqndzq:XXX	success	3429	United Kingdom, London	UK-2 Limited	true	true

And here's how they look in the RSS Retriever settings, with passwords XXXd out:

taeqndzq:XXX@45.38.107.97:6014
taeqndzq:XXX@23.95.150.145:6114
taeqndzq:XXX@198.23.239.134:6540

CyberSEO on Known good proxies fail to connect

Thu, 04 Sep 2025 17:41:10 +0200

RSS Retriever supports authenticated proxies. However, if the credentials are missing or not parsed correctly, the connection will fail.

Unfortunately, we can't debug third-party proxies here, especially since you don't want to post your login information publicly. The best next step is to test those proxies in an environment where you can enter the full credentials. For example, you could use a local cURL command on your own machine or a private proxy checker that accepts username and password authentication.

If they can access cURL locally with the same credentials but cannot access the plugin, there is likely an issue with how the proxy format is specified in the plugin settings. If so, please contact by email so we can review the format together. Otherwise, it most likely means that the proxy itself is not accepting connections from your host.

davet3929 on Known good proxies fail to connect

Thu, 04 Sep 2025 17:21:13 +0200

The IPs have associated login/passwords that don't show up in the log. Without the login info I'm not surprised that proxyscrape says the IPs are dead. So how do I debug this without publicly posting my passwords on this forum?

CyberSEO on Known good proxies fail to connect

Thu, 04 Sep 2025 16:58:26 +0200

davet3929 on Known good proxies fail to connect

Thu, 04 Sep 2025 16:50:05 +0200

I have some proxy servers that checkout OK on Login to see this link, but on RSS Retriever they all fail with "Couldn't connect to server" (see log below). How can I debug this?

Login to see the quote