I have a large set of projects to edit on Anitya to fix the homepages but when submitting the change I keep getting this error:
504 Gateway Time-out The server didn't respond in time.
Is there anything that can be done to fix that?
Thank you and wishing you happy holidays.
Does the timeout page have any other info on it?
Can you look at the page with the firefox or chrome inspector and see what exact ip address it came back from?
Metadata Update from @kevin: - Issue priority set to: Waiting on Assignee (was: Needs Review)
Does the timeout page have any other info on it? Can you look at the page with the firefox or chrome inspector and see what exact ip address it came back from?
There's no other info on it. That's the Response I get from the server:
HTTP/2.0 504 Gateway Timeout date: Mon, 23 Dec 2019 20:32:21 GMT server: Apache strict-transport-security: max-age=31536000; includeSubDomains; preload x-frame-options: SAMEORIGIN x-xss-protection: 1; mode=block x-content-type-options: nosniff referrer-policy: same-origin cache-control: no-cache content-type: text/html apptime: D=30012077 x-fedora-proxyserver: proxy01.phx2.fedoraproject.org x-fedora-requestid: XgEkVbThfs7M7h@ay1GrhQAAAA8 X-Firefox-Spdy: h2
Metadata Update from @mizdebsk: - Issue tagged with: release-monitoring
maybe related: i try to add a package mapping 504 Gateway Time-out The server didn't respond in time.
or via api: HTTP/2 504 date: Wed, 01 Jan 2020 17:13:26 GMT server: Apache strict-transport-security: max-age=31536000; includeSubDomains; preload x-frame-options: SAMEORIGIN x-xss-protection: 1; mode=block x-content-type-options: nosniff referrer-policy: same-origin cache-control: no-cache content-type: text/html apptime: D=30009382 x-fedora-proxyserver: proxy01.phx2.fedoraproject.org x-fedora-requestid: XgzTNrIaII8Z3bEy7rhUSwAAAAE
<html><body>
Is this still happening?
Not right now, but it was happening after I edited several project in a row. I don't have anything to edit anymore so I can't check if it is still happening.
Let's close this for now, feel free to reopen it if you experience the problem again
Metadata Update from @cverna: - Issue close_status updated to: Insufficient data - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.