Skip to content

Lazy server guide: use connect vs read timeout for paused servers #178

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
TBlueF merged 1 commit into from
Aug 7, 2026
Merged

Lazy server guide: use connect vs read timeout for paused servers #178

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion community/BluemapLazyServer.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -96,7 +96,7 @@ server {
# Proxy all requests for live data to the integrated webserver.
# Fall back to @server-offline if it can't be contacted.
location ~* ^/maps/[^/]*/live/ {
proxy_read_timeout 2s; # required if lazymc pauses the server instead of shutting it down
proxy_connect_timeout 2s; # required if lazymc pauses the server instead of shutting it down
error_page 502 504 = @server-offline;
proxy_pass http://127.0.0.1:8100; # the default port for the integrated webserver, adapt to your setup
}
Expand Down