-
-
Notifications
You must be signed in to change notification settings - Fork 5.6k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Cannot modify 'Request Timeout (Timeout after XX seconds)' #5445
Comments
@nowniz, If I’m correct, the minimum values are 20 seconds when setting the following settings: |
@homelab-alpha , The screen above showing the change process from 16s to 12s is an example. In reality, if �I click 'save' with over 20 seconds value has changed more than most values, it's retaining the previous value before keeping it changed. |
@nowniz, It seems that a calculation is being performed in the background involving the Although the minimum value for both the Based on my testing, it is possible to set the Personally, I don’t fully understand the logic behind this calculation. Is there a specific reason for setting it lower than 16 seconds? |
@homelab-alpha , So, isn't it possible to set only the Request Response value separately and separately? |
@nowniz, I'm not sure about that. It seems that it's not possible if the other two have a minimum value of 20 seconds. |
🛡️ Security Policy
📝 Describe your problem
The item in each monitor > Edit > General > 'Request Timeout' does not change from previous value
For exampple, even if I change a number other than 16 and click 'Save', the status value is reflected as 16.
I am using the Docker version with the beta tag, but I would like to inquire whether the bug only occurs in that version.
📝 Error Message(s) or Log
🐻 Uptime-Kuma Version
2.0.0-beta.0
💻 Operating System and Arch
Amazon Linux release 2023.4.20240401, Docker
🌐 Browser
Google Chrome 128.0.6613.120
🖥️ Deployment Environment
The text was updated successfully, but these errors were encountered: