Log In
Home
(0 votes) 12:56 pm
January 22, 2023
Offline
hi guys,
Since Feb 8th, CyberSEO PRO started to fail processing posts. Here is an example below:
Login to see the quote
This is the same for all URLs trying to parse, no posts is added at all and I believe the plugin update on or around Feb 8th has ruined.
Plugin was working fine with all functions including OpenAI integration that I was testing.
Please guide me on what to do since the plugin version is already updated to latest version: CyberSEO Pro ver. 10.038
1:04 pm
July 2, 2009
Offline
I've checked your feed and here is the Syndicator Log for it:
Login to see the quote
So it's definitely not CyberSEO Pro, but the site you are trying to pull this feed from. I believe your server IP was banned by the site owner.
ChatGPT suggests to use proxies in this case: Login to see this link
3:43 pm
January 22, 2023
Offline
Thanks,
But I'm not familiar with proxies to be used in WordPress. Is there any suggested/trusted list of proxies?
Proxy websites don't seem so trustworthy.
3:46 pm
July 2, 2009
Offline
Proxies are not made for WordPress. They are made to hide an IP of your server. Please read this article: Login to see this link
The CyberSEO Pro plugin works with any proxies, including those that require login and password for access.
3:55 pm
January 22, 2023
Offline
Hi, I wanted to reply to this again.
I purchased residential proxies from IP Royals and included a bunch of proxy addresses in following format:
USERNAME:PASSWORD@HOSTNAME:PORT
RSS Syndication still not working, but this time with the following log:
Login to see the quote
I also get "XML parse error 68." and "CyberSEO parser error: 68 (XML_ERR_NAME_REQUIRED). Perhaps the feed is unreachable, broken or empty." warning on Wordpress screen when I try to edit a feed.
Any help is much appreciated. I really want it work.
Best,
3:58 pm
July 2, 2009
Offline
Please email @ Login to see this link. It looks like something is wrong with the cURL request via proxy, so perhaps an access to your WordPress dashboard will be needed.
9:43 pm
July 2, 2009
Offline
I've checked your proxy. It returns the HTTP 402 status code. This error message indicates that your request to the proxy server was successful, but when the proxy attempted to connect to the target server using the CONNECT method, it received an HTTP 402 response.
The HTTP 402 status code is not a standard HTTP status code and is not defined in any RFCs. However, it is often used to indicate that the request was not fulfilled due to payment or subscription issues. This means that the proxy server may be requiring payment or authentication to access the target server.
All RSSMost Users Ever Online: 541
Currently Online:
12 Guest(s)
Currently Browsing this Page:
1 Guest(s)
Top Posters:
ninja321: 84
s.baryshev.aoasp: 68
Freedom: 61
Pandermos: 54
MediFormatica: 49
B8europe: 48
Member Stats:
Guest Posters: 337
Members: 2816
Moderators: 0
Admins: 1
Forum Stats:
Groups: 1
Forums: 5
Topics: 1625
Posts: 8271
Newest Members:
jeremyboucher, lthompson2709, MAC, duty3canada, backlinkmorocco, dmitrypehovskiworkAdministrators: CyberSEO: 3909