Please confirm the following.
What browsers are you seeing the problem on?
Firefox
Describe the bug
Hello,
I am receiving a database error when trying to use the Modrinth website (specifically when performing actions that interact with the API / login / search).
The main page loads with a 200 OK status, but internal actions trigger the following error from your backend:
"MISCONF: Valkey is configured to save RDB snapshots, but it's currently unable to persist to disk. Commands that may modify the data set are disabled, because this instance is configured to report errors during writes if RDB snapshotting fails (stop-writes-on-bgsave-error option)."
It also occasionally throws Cannot assign requested address (os error 99) for the Redis Pool. It seems like one of your backend nodes or Valkey instances has run out of disk space or hit Linux memory overcommit limits.
Could you please check the Valkey logs and server storage? Thanks!
Steps to reproduce
Go to modrinth.com (the main page might load normally).
Try to log in, use the search bar, or interact with any feature that sends requests to the backend API.
See the raw JSON database error or console network errors.
Expected behavior
The website should process API requests normally, allow users to log in, search for mods, and interact with the database without throwing backend persistence errors.
Additional context
The issue seems node-specific or routing-dependent, as some users on other networks/OS routes report it working, while others hit this failing Valkey instance completely blocking any write/session commands. Hard refreshing and using a VPN doesn't bypass the node if cached by Cloudflare routing on this end. Please check the Valkey/Redis logs and server storage. Thanks!
Please confirm the following.
What browsers are you seeing the problem on?
Firefox
Describe the bug
Hello,
I am receiving a database error when trying to use the Modrinth website (specifically when performing actions that interact with the API / login / search).
The main page loads with a 200 OK status, but internal actions trigger the following error from your backend:
"MISCONF: Valkey is configured to save RDB snapshots, but it's currently unable to persist to disk. Commands that may modify the data set are disabled, because this instance is configured to report errors during writes if RDB snapshotting fails (stop-writes-on-bgsave-error option)."
It also occasionally throws Cannot assign requested address (os error 99) for the Redis Pool. It seems like one of your backend nodes or Valkey instances has run out of disk space or hit Linux memory overcommit limits.
Could you please check the Valkey logs and server storage? Thanks!
Steps to reproduce
Go to modrinth.com (the main page might load normally).
Try to log in, use the search bar, or interact with any feature that sends requests to the backend API.
See the raw JSON database error or console network errors.
Expected behavior
The website should process API requests normally, allow users to log in, search for mods, and interact with the database without throwing backend persistence errors.
Additional context
The issue seems node-specific or routing-dependent, as some users on other networks/OS routes report it working, while others hit this failing Valkey instance completely blocking any write/session commands. Hard refreshing and using a VPN doesn't bypass the node if cached by Cloudflare routing on this end. Please check the Valkey/Redis logs and server storage. Thanks!