tickets #124559
closed
Added by ilausuch over 1 year ago.
Updated 12 months ago.
Description
Hi,
I have problems to connect to progress if I use the IP that my ISP give to me (185.234.246.104 ). I have timeouts. The ISP doesn’t change the IP neither if I restart the router, but I can use progress with a public VPN. But it will be better to have access to progress with my IP.
I having using the progress API a lot because I am doing a project that requires querying. Maybe I raised some kind of limit.
Thank you
Best regards
- Private changed from Yes to No
I am not aware of any traffic limits for progress.o.o
There is indeed a limit for login2.o.o (that's the login proxy for progress and some other services) which we set up some months ago to stop a DOS attack.
Querying the API a lot might trigger that limit (IIRC 255 connections per minute).
To get un-blocked again, do not do any connection attempt to a service behind login2.o.o for 6 minutes.
Please report back if this fixed the issue for you (AFAIK you are the first human who hit the limit).
Hi, I am afraid this still not works for me
I checked these on both proxy machines, all with no output:
$ grep 185.234.246.104 /proc/1/net/xt_recent/https2
$ iptables -L|grep 185.234.246.104
$ grep 185.234.246.104 /var/log/apache2/progress-*log
$ xzgrep 185.234.246.104 /var/log/apache2/progress-*log*.xz
Do you still encounter this issue? If so, can you elaborate on "timeouts", which software reports them with which messages? Can you provide traceroute output?
- Status changed from New to Closed
Also available in: Atom
PDF