You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
If you going to publish in Nginx , I highly recommend you this configuration,
`server {
server_name awesomeblog.com;
}`
to avoid this issues
2025/03/26 11:24:47 [error] 161414#161414: *6453 upstream prematurely closed connection while reading response header from upstream, client: 177.224.183.8, server:awesomeblog.com, request: "GET / HTTP/1.1", upstream: "http://127.0.0.1:5002/", host: "awesomeblog.com" 2025/03/26 11:29:08 [error] 161414#161414: *6499 upstream sent too big header while reading response header from upstream, client: 177.224.183.8, server: awesomeblog.com, request: "POST /manager/login?ReturnUrl=%2Fmanager HTTP/1.1", upstream: "http://127.0.0.1:5002/manager/login?ReturnUrl=%2Fmanager", host: "awesomeblog.com", referrer: "https://awesomeblog.com/manager/login?ReturnUrl=%2Fmanager"
Beta Was this translation helpful? Give feedback.
All reactions