Jump to content

Reporting problems today?


mrmaxx

Recommended Posts

  • Replies 712
  • Created
  • Last Reply

Just now (the problem seems to of started when we got the Graph back)

Gateway Timeout

The proxy server did not receive a timely response from the upstream server.

Reference #1.e2c1093d.1341267203.6d76522

Link to comment
Share on other sites

For the past week or more your service has become unuseable, wating my time in reporting spam issues as SpamCop seems unable to control its affairs in handling reported spam issues.

Sorry folks, if this ain't fixed I won't be working with you any more, you are now wasting more of my time that the spam junk I have to deal with.

newsmedianews.com

Merged into this article from a separate new post called "service now unuseable" to SpamCop Forum "SpamCop Email System & Accounts" by Steve T

Link to comment
Share on other sites

It looks like things are back to normal now.

Let me know if you see more problems.

- Don D'Minion - SpamCop Admin -

- Service[at]Admin.SpamCop.net -

I've been getting gateway timeouts all day, (Actually for about 2 weeks now). These are from today:

Gateway Timeout

The proxy server did not receive a timely response from the upstream server.

Reference #1.8c70e93f.1341274159.10041c3

Reference #1.8c70e93f.1341274159.10041af

Reference #1.8c70e93f.1341274159.10041a6

Reference #1.8c70e93f.1341274158.1004179

Reference #1.8c70e93f.1341273959.ff741d

Reference #1.8c70e93f.1341273958.ff73f9

Reference #1.8c70e93f.1341273958.ff73f8

Reference #1.8c70e93f.1341273958.ff73d9

Reference #1.8c70e93f.1341273958.ff73d2

Reference #1.8c70e93f.1341273958.fe342a

Link to comment
Share on other sites

Hi, all!

My 2 cents' worth:

Just logged in after about a 3 minute delay.

Tried reporting spam before, got the same error as everyone else:

"Gateway Timeout

The proxy server did not receive a timely response from the upstream server.

Reference #1.c402e9dc.1341273890.1a0963cc"

I now have the "Unreported spam Saved:Report Now" link.

I clicked on the link, and got (after a long delay):

Gateway Timeout

The proxy server did not receive a timely response from the upstream server.

Reference #1.c602e9dc.1341275621.22e21bf6

If my experience over the last few weeks is anything to go by, I would expect that it

will come good in a couple of hours.

I'm in Sydney, Australia, (UTC+10:00), and it always seems to play up between about

07:00 and 11:00 (my time), and then comes good during my late morning / early afternoon time.

It has been doing this for about 3 or 4 weeks now.

Link to comment
Share on other sites

Update: Reporting seems to be working OK now.

Just managed to clear the unreported spam, no undue delays.

Hope it stays OK!

Link to comment
Share on other sites

I've been getting gateway timeouts all day, (Actually for about 2 weeks now). These are from today:

Gateway Timeout

The proxy server did not receive a timely response from the upstream server.

Reference #1.8c70e93f.1341274159.10041c3

Reference #1.8c70e93f.1341274159.10041af

Reference #1.8c70e93f.1341274159.10041a6

Reference #1.8c70e93f.1341274158.1004179

Reference #1.8c70e93f.1341273959.ff741d

Reference #1.8c70e93f.1341273958.ff73f9

Reference #1.8c70e93f.1341273958.ff73f8

Reference #1.8c70e93f.1341273958.ff73d9

Reference #1.8c70e93f.1341273958.ff73d2

Reference #1.8c70e93f.1341273958.fe342a

Finally all the above went through! :lol:

Still having issues though <_< , but I was able to eventually get my last 13 spams through. :)

Link to comment
Share on other sites

I'm getting severe "Gateway Timeout" problems when attempting to report spam today and it seems to have been happening off and on for the past few weeks. (Because of the mechanics of the way I report spam on my Mac with keyboard shortcuts, etc, the hangs on the website make it much more painful and long winded to report spam when the hanging/ "Gateway Timeout" problem occurs),

William

Link to comment
Share on other sites

It has been something like following on and off for few days now:

After clicking Report Now and waited for long time:

Gateway Timeout

The proxy server did not receive a timely response from the upstream server.

Reference #1.7cc08d3f.1341326922.57fc465

or

SpamCop v 4.6.2.001 © 1992-2012 Cisco Systems, Inc. All rights reserved.

Here is your TRACKING URL - it may be saved for future reference:

http://www.spamcop.net/sc?id=z5364415587z0...c328939b95040bz

Other times, I got following when I tried to reload the page at http://members.spamcop.net/:

An error occurred while processing your request.

Reference #97.2dc731d0.1341332888.1657c59

It just like SpamCop suffers from distributed denial-of-service attack (DDoS attack). :(

Link to comment
Share on other sites

Props to the engineers! It all seems to be working fine now.....all last night I kept getting the Gateway Timeouts....now it's golden ;) Reporting all my spam just fine via the web interface.....

EDIT: Seems to be back :P

Gateway Timeout

The proxy server did not receive a timely response from the upstream server.

Reference #1.14354317.1341331619.498e6fa7

Link to comment
Share on other sites

Props to the engineers! It all seems to be working fine now.....all last night I kept getting the Gateway Timeouts....now it's golden ;) Reporting all my spam just fine via the web interface.....

Not tempting providence, but all seems fixed again here.... Can anyone tell us what the problem/fix was?

Link to comment
Share on other sites

the trouble happen to free user accounts, or to payd accounts too?

Appears to be both.

Damn! why did I open my big mouth?

Back to huge delays and timeouts :-(

As stated much, much earlier, it appears to be up and down. Seems to be taking a long time to fix.

Link to comment
Share on other sites

Gateway Timeout

The proxy server did not receive a timely response from the upstream server.

Reference #1.c4a0adc6.1341337749.5434b198

Gateway Timeout

The proxy server did not receive a timely response from the upstream server.

Reference #1.1fa32ed0.1341338309.1914acc4

Link to comment
Share on other sites

Now I seem to have a new problem. The reporting page hung for a rather long time and instead of giving a gateway timeout, I got this instead:

Parsing header:

got sigalarm, taking too long to process, aborted.

Perhaps you can wait a few minutes and reload?

William

Link to comment
Share on other sites

I got this feeling we're looking at a typo in a scheduled maintenance command in which something that's supposed to be running on, say, a weekly basis, is running hourly?

Which would explain the on again, off again, ability to run the parser without delay.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.


×
×
  • Create New...