"Tempoarily out of resourse, please try again later." Error Message in Web Browser
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
"Tempoarily out of resourse, please try again later." Error Message in Web Browser
Hi!
I have a Slackware machine which I configured so that NAT works on it.
It is Slackware-current with 2.6.12.3 compiled using gcc4.0 which is compiled on the machine itself.
Now, I have been getting the following message on my browsers regardless of operating system (Linux, Mac Os X, or Windows): (Note the spelling mistakes are not my work, am quoting verbatim.)
Code:
Tempoarily out of resourse, please try again later.
Intermittently I get the message while browsing the Internet, a simple click of reload will bring me to the web page I intended to go.
I notice this started happening lately after a tcpip, iptables, etc upgrades. But it has reduced (one time today) after peaking a few days ago.
But, I am getting that error even in Safari and Camino.
Yesterday, I tried browsing using Firefox on Slackware, I get that error message twice in very short period. And, with Slackware machine not running any progs, I have not been getting it.
Oh, another note, I did use bittorrent, could it be that the new iptables or tcpip is limitting the number of connections?
Note, I did not touch iptables rules.
Edit:
And, my camino, firefox, etc. Are set to use high maximum connections.
Originally posted by carboncopy But, I am getting that error even in Safari and Camino.
Yesterday, I tried browsing using Firefox on Slackware, I get that error message twice in very short period. And, with Slackware machine not running any progs, I have not been getting it.
Oh, another note, I did use bittorrent, could it be that the new iptables or tcpip is limitting the number of connections?
Note, I did not touch iptables rules.
Edit:
And, my camino, firefox, etc. Are set to use high maximum connections.
hmmm... what's your current ephemeral port range??
Distribution: Slackware 13; Ubuntu Raspberry Pi OS
Posts: 255
Rep:
Believe it or not, I think that is a server error 503, and the server has too many connections on it. When you hit refresh there is a connection available and it lets you in.
Originally posted by n0xvb Believe it or not, I think that is a server error 503, and the server has too many connections on it. When you hit refresh there is a connection available and it lets you in.
I'd bet it's coincidental to your upgrades.
The thing is, it is purely random. And it happens even with almost omni-potent sites, such as IBM, BBC etc.
And if it is error 503, the browser will catch it its own error message.
It is still happening today. Even without bittorrent running, single client connected to Slackware (NAT machine).
basically, it's the range of (source) ports your box will use when making connections to remote boxes... try increasing the range a little to see if it helps, although you have a pretty wide range set already:
what's your tcp fin timeout set to?? you can check with:
Code:
cat /proc/sys/net/ipv4/tcp_fin_timeout
if it's set to something like 180 bring it down to 30:
Code:
echo "30" > /proc/sys/net/ipv4/tcp_fin_timeout
then see if the problem continues...
on a side note, i had a similar problem for the past couple weeks, i was suspecting it was my squid proxy server but it ended up being my ISP's DNS servers that were messed-up... if you wanna look at the thread it's this one:
Originally posted by carboncopy Will this setting stays this way? Or do I have to include it into rc.local? Or is there some config file somewhere?
yeah, it'll be gone upon reboot, so you need to put the echoes in rc.local or similar... BTW, if you're on slackware it's common to instead use the rc.firewall script for this...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.