Meddelande: 04 Gateway Time-out nginx/1.4.6 (Ubuntu)

Vad betyder detta? Är det fel på sajten jag förgäves försöker komma in på? Eller har jag fått virus i datorn?

Hjälper inte att googla, det står bara en massa på engelska som jag inte begriper.

Ser du det på din skärm är det andra änden som inte fungerar. Det är svaret från en annan dator.

Tack, då är det inte något jag kan göra själv, bara att hoppas på att det försvinner.

Bump!

Ännu ett mysko meddelande när jag försöker komma in på en sajt:

502 Bad Gateway
nginx/1.18.0 (Ubuntu)

Jag googlar men blir inte klokare. En sajt erbjuder att man ska ladda ner ett program:

https://wikifixes.com/sv/errors/0x/gate ... ror%20502/

Men jag blir inte klok på vad det innebär. En jättehög kostnad som jag uppdagar för sent? Ett program fullt med trojaner?

Gateway betyder portvalv, alltså en väg genom en inhägnad som kan blockeras av en port/grind. I överförd betydelse en flaskhals i kommunikationen mellan datorer. Du har en router mellan datorn och Internet och det finns även en router (eller liknande apparat) mellan Internet och den server webbplatsen du försöker nå ligger på. Eftersom du kan skriva här kan det inte vara fel på din router, utan det sitter i den andra routern som webbplatsen ligger bakom. Det finns inget du kan göra åt detta (annat än att kontakta webbplatsägaren och påtala problemet).

Programmet i din länk kan bara ändra saker på din dator och därför inte hjälpa dig med detta. Sidan bör betraktas som reklam.

Alien skrev:Ännu ett mysko meddelande när jag försöker komma in på en sajt:

502 Bad Gateway
nginx/1.18.0 (Ubuntu)

Det är ett fel i andra änden och inget som du kan göra något åt.

Tack, så alla meddelanden som börjar med Gateway betyder att det är fel i andra ändan. Då är det bara att ge upp/försöka igen senare.

Tyvärr får jag många andra meddelanden också...

Inte riktigt så, men det där är ett felmeddelande från webservern i andra änden. Jag orkar inte förklara pedagogiskt.

En enkel grundregel är att börjar meddelandet på 5xx (grönt nedanför) så är felet i andra änden (dvs servern).
Om felmeddelandet däremot börjar på 4xx (rött nedanför) så är felet på din sida.

Kort sagt betyder Gateway Timeout, att en lastbalanserare inte får kontakt med den inre servern. Dvs en hemsida har en lastbalanserare som skickar din förfrågan till en av flera servrar för att sprida ut antalet besökare så att inte en enskild server blir överbelastad.
När en uppströms server blir överbelastad eller får driftavbrott, så svarar lastbalanseraren till dig med en "504 Gateway Timeout" eftersom lastbalanseraren inte får kontakt med någon av originalservrarna.

Ett tips är att läsa RFC 9110: https://datatracker.ietf.org/doc/html/rfc9110
särskilt kapitel 15, från nr 5 och framåt, så förstår du vad det handlar om:

15.5. Client Error 4xx

The 4xx (Client Error) class of status code indicates that the client
seems to have erred. Except when responding to a HEAD request, the
server SHOULD send a representation containing an explanation of the
error situation, and whether it is a temporary or permanent
condition. These status codes are applicable to any request method.
User agents SHOULD display any included representation to the user.

15.5.1. 400 Bad Request

The 400 (Bad Request) status code indicates that the server cannot or
will not process the request due to something that is perceived to be
a client error

15.5.2. 401 Unauthorized

The 401 (Unauthorized) status code indicates that the request has not
been applied because it lacks valid authentication credentials for
the target resource.

15.5.3. 402 Payment Required

The 402 (Payment Required) status code is reserved for future use.

15.5.4. 403 Forbidden

The 403 (Forbidden) status code indicates that the server understood
the request but refuses to fulfill it. A server that wishes to make
public why the request has been forbidden can describe that reason in
the response content (if any).

15.5.5. 404 Not Found

The 404 (Not Found) status code indicates that the origin server did
not find a current representation for the target resource or is not
willing to disclose that one exists.

15.5.6. 405 Method Not Allowed

The 405 (Method Not Allowed) status code indicates that the method
received in the request-line is known by the origin server but not
supported by the target resource.

15.5.7. 406 Not Acceptable

The 406 (Not Acceptable) status code indicates that the target
resource does not have a current representation that would be
acceptable to the user agent, according to the proactive negotiation
header fields received in the request (Section 12.1), and the server
is unwilling to supply a default representation.

15.5.8. 407 Proxy Authentication Required

The 407 (Proxy Authentication Required) status code is similar to 401
(Unauthorized), but it indicates that the client needs to
authenticate itself in order to use a proxy for this request.

15.5.9. 408 Request Timeout

The 408 (Request Timeout) status code indicates that the server did
not receive a complete request message within the time that it was
prepared to wait.

15.5.10. 409 Conflict

The 409 (Conflict) status code indicates that the request could not
be completed due to a conflict with the current state of the target
resource.

15.5.11. 410 Gone

The 410 (Gone) status code indicates that access to the target
resource is no longer available at the origin server and that this
condition is likely to be permanent.

15.5.12. 411 Length Required

The 411 (Length Required) status code indicates that the server
refuses to accept the request without a defined Content-Length
(Section 8.6).

15.5.13. 412 Precondition Failed

The 412 (Precondition Failed) status code indicates that one or more
conditions given in the request header fields evaluated to false when
tested on the server (Section 13).

15.5.14. 413 Content Too Large

The 413 (Content Too Large) status code indicates that the server is
refusing to process a request because the request content is larger
than the server is willing or able to process.

15.5.15. 414 URI Too Long

The 414 (URI Too Long) status code indicates that the server is
refusing to service the request because the target URI is longer than
the server is willing to interpret.

15.5.16. 415 Unsupported Media Type

The 415 (Unsupported Media Type) status code indicates that the
origin server is refusing to service the request because the content
is in a format not supported by this method on the target resource.

15.5.17. 416 Range Not Satisfiable

The 416 (Range Not Satisfiable) status code indicates that the set of
ranges in the request's Range header field (Section 14.2) has been
rejected either because none of the requested ranges are satisfiable
or because the client has requested an excessive number of small or
overlapping ranges (a potential denial of service attack).

15.5.18. 417 Expectation Failed

The 417 (Expectation Failed) status code indicates that the
expectation given in the request's Expect header field
(Section 10.1.1) could not be met by at least one of the inbound
servers.

15.5.19. 418 (Unused)

[RFC2324] was an April 1 RFC that lampooned the various ways HTTP was
abused; one such abuse was the definition of an application-specific
418 status code, which has been deployed as a joke often enough for
the code to be unusable for any future use.

15.5.20. 421 Misdirected Request

The 421 (Misdirected Request) status code indicates that the request
was directed at a server that is unable or unwilling to produce an
authoritative response for the target URI.

15.5.21. 422 Unprocessable Content

The 422 (Unprocessable Content) status code indicates that the server
understands the content type of the request content (hence a 415
(Unsupported Media Type) status code is inappropriate), and the
syntax of the request content is correct, but it was unable to
process the contained instructions.

15.5.22. 426 Upgrade Required

The 426 (Upgrade Required) status code indicates that the server
refuses to perform the request using the current protocol but might
be willing to do so after the client upgrades to a different
protocol. The server MUST send an Upgrade header field in a 426
response to indicate the required protocol(s) (Section 7..

================================================================================

15.6. Server Error 5xx

The 5xx (Server Error) class of status code indicates that the server
is aware that it has erred or is incapable of performing the
requested method. Except when responding to a HEAD request, the
server SHOULD send a representation containing an explanation of the
error situation, and whether it is a temporary or permanent
condition. A user agent SHOULD display any included representation
to the user. These status codes are applicable to any request
method.

15.6.1. 500 Internal Server Error

The 500 (Internal Server Error) status code indicates that the server
encountered an unexpected condition that prevented it from fulfilling
the request.

15.6.2. 501 Not Implemented

The 501 (Not Implemented) status code indicates that the server does
not support the functionality required to fulfill the request. This
is the appropriate response when the server does not recognize the
request method and is not capable of supporting it for any resource.

15.6.3. 502 Bad Gateway

The 502 (Bad Gateway) status code indicates that the server, while
acting as a gateway or proxy, received an invalid response from an
inbound server it accessed while attempting to fulfill the request.

15.6.4. 503 Service Unavailable

The 503 (Service Unavailable) status code indicates that the server
is currently unable to handle the request due to a temporary overload
or scheduled maintenance, which will likely be alleviated after some
delay.

15.6.5. 504 Gateway Timeout

The 504 (Gateway Timeout) status code indicates that the server,
while acting as a gateway or proxy, did not receive a timely response
from an upstream server it needed to access in order to complete the
request.

15.6.6. 505 HTTP Version Not Supported

The 505 (HTTP Version Not Supported) status code indicates that the
server does not support, or refuses to support, the major version of
HTTP that was used in the request message.

Bra, sköna svar.
För att spela viktig - här nu. Kan även vara en ingress controller, ej exakt samma sak som load... nära på dock, som spökar, Alien.
"Tyvärr får jag många andra meddelanden också..."
Hoppas det fungerar nu iaf.