You are not logged in.
- Topics: Active | Unanswered
Pages: 1
#1 2020-01-12 7:32 pm
- hellbyte
- Member
- Registered: 2020-01-10
- Posts: 3
Can not query API
Hello,
I have noticed connection freezes on form submit on my website. I checked error logs from my MODX cms and noticed that it cannot connect to http://api.stopforumspam.org/
Then i tried to check it manually, error was confirmed after a long delay I got an answer:
wget http://api.stopforumspam.org/api
--2020-01-12 21:24:03-- http://api.stopforumspam.org/api
Resolving api.stopforumspam.org... 192.124.249.168, 2a02:fe80:1010::18:2
Connecting to api.stopforumspam.org|192.124.249.168|:80... connected.
HTTP request sent, awaiting response... 502 Bad Gateway
2020-01-12 21:24:35 ERROR 502: Bad Gateway.
However I can successfully connect to http://api.stopforumspam.org/ without api in the end.
A few days ago problem was present at different IP's and networks of one provider. Today I found that it stopped working from IP of another ISP, so the problem is probably at SFS end.
If I open /api in browser I get cloudflare's error:
Error 502 Ray ID: 55417fff73f08b0e • 2020-01-12 19:23:05 UTC
Bad gateway
Someone else have same issues ? any ideas ?
Offline
#2 2020-01-13 5:57 am
- Oblivian
- Member
- Registered: 2018-11-04
- Posts: 79
Re: Can not query API
.com, .org depreciated
https://www.stopforumspam.com/forum/viewtopic.php?id=8954
Offline
#3 2020-01-13 1:30 pm
- hellbyte
- Member
- Registered: 2020-01-10
- Posts: 3
Re: Can not query API
if both .com and .org are not deprecated, what addr should be used then ?
First ISP, both .com and .org is not working:
# wget http://api.stopforumspam.com/api
--2020-01-13 15:24:46-- http://api.stopforumspam.com/api
Resolving api.stopforumspam.com... 104.25.136.22, 104.25.137.22, 2606:4700:20::6819:8916, ...
Connecting to api.stopforumspam.com|104.25.136.22|:80... connected.
HTTP request sent, awaiting response... 502 Bad Gateway
2020-01-13 15:25:17 ERROR 502: Bad Gateway.
# wget http://api.stopforumspam.org/api
--2020-01-13 15:26:16-- http://api.stopforumspam.org/api
Resolving api.stopforumspam.org... 192.124.249.168, 2a02:fe80:1010::18:2
Connecting to api.stopforumspam.org|192.124.249.168|:80... connected.
HTTP request sent, awaiting response... 502 Bad Gateway
2020-01-13 15:26:47 ERROR 502: Bad Gateway.
Another ISP:
Today .org is WORKING and .com is NOT working. But 2-3 days ago at this isp .com worked.
Offline
#4 2020-01-13 1:48 pm
- Snowhog
- Member
- From: Minnesota
- Registered: 2012-09-09
- Posts: 60
- Website
Re: Can not query API
Access site using https://
Administrator - Kubuntu Forums . Net
"It is a capital mistake to theorize before one has data." - Sherlock Holmes
Using Kubuntu Linux since March 23, 2007
Offline
#5 2020-01-13 9:22 pm
- Alex Kemp
- Moderator
- From: Nottingham, England
- Registered: 2009-12-02
- Posts: 2,423
- Website
Re: Can not query API
The current SFS examples on using the API show a HTTP (rather than HTTPS) url. That was because of a significant number of ISPs having problems issuing HTTPS accesses (and yes, I agree, that is bizarre in 2020 yet it is what some folks still have to deal with).
Use a HTTPS url if you possibly can.
Offline
#6 2020-01-14 1:05 am
- hellbyte
- Member
- Registered: 2020-01-10
- Posts: 3
Re: Can not query API
https - same behaviour. But I have found the reason. The problem is reproducing when request is empty (no arguments provided). Bug is present on ISP1 (both .com and .org domains) and on ISP2 (problem only at .com, .org - is ok).
According to call without arguments to .org domain from ISP2 result should be:
<response success="false">
<error>request not understood</error>
</response>
So O think it is a problem on server side when processing GET arguments
Offline
#7 2020-01-14 5:52 am
- Alex Kemp
- Moderator
- From: Nottingham, England
- Registered: 2009-12-02
- Posts: 2,423
- Website
Re: Can not query API
I've pinged pedigree (and thanks for that helpful feedback).
Offline
#8 2020-01-19 8:02 am
- pedigree
- uıɐbɐ ʎɐqǝ ɯoɹɟ pɹɐoqʎǝʞ ɐ buıʎnq ɹǝʌǝu ɯ,ı
- From: New Zealand
- Registered: 2008-04-16
- Posts: 7,056
Re: Can not query API
passing the api no data should give a 502 error, not a bad gateway error but it's generating one anyway. i'll go over all the rules when im back from the nightmare of travel, but the api will shortly be running entirely on the cloudflare serverless platform, which will handle all the mixtures of domains
Offline
#9 2020-01-19 8:12 am
- pedigree
- uıɐbɐ ʎɐqǝ ɯoɹɟ pɹɐoqʎǝʞ ɐ buıʎnq ɹǝʌǝu ɯ,ı
- From: New Zealand
- Registered: 2008-04-16
- Posts: 7,056
Re: Can not query API
i've checked all the nodes and they're all working. if your provider is messing with the http connection then you could get that error. i dont see sucuri with any new endpoints that i need to have added to the firewall, and i cant replicate a 502, only a 503
Offline
Pages: 1