I have…
- Read the following guideline: Troubleshooting and Support | Squidex. I understand that my support request might get deleted if I do not follow the guideline.
- Used code blocks with ``` to format my code examples like JSON or logs properly.
I’m submitting a…
- Regression (a behavior that stopped working in a new release)
- Bug report
- Performance issue
- Documentation issue or request
Current behavior
status code 408 for APIs request
Expected behavior
Minimal reproduction of the problem
Environment
App Name:
- Self hosted with docker
- Self hosted with IIS
- Self hosted with other version
- Cloud version
Version: [VERSION]
Browser:
- Chrome (desktop)
- Chrome (Android)
- Chrome (iOS)
- Firefox
- Safari (desktop)
- Safari (iOS)
- IE
- Edge
Others:
Sorry, I have never received a warning about that. I have OneUptime and Google Cloud agents that monitor the state and create notifications and there was nothing. I have restarted the servers and hope it has been fixed.
I have restarted the nodes. Not sure if it helps.
I did some debugging last night and found that some endpoints were still working, mostly the less heavy ones.
The larger ones and a lot of graphQL stuff seemed to timeout.
Not sure if that helps you.
Yes, the load on the database was really go up like crazy:
I have restarted the nodes one by one, but of course this does not solve the root cause.
Seems to be fixed now,
Keep us posted on your findings on the root cause. I will need the information for a report to the clients
Yes, but it will be super difficult. The CPU is not going up anymore, which is very strange.
No worries!
Probably not related by it seemed to happen exactly at the time that I added new content to a project. Probably just a coincidence… thought I broke everything at the time, was fun haha
Not so funny 
…but not very likely.
I have not found the root cause yet, but I have created an alert for CPU usage.
