-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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.
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
Portainer local unresponsive and slow #12354
Comments
What are the specs of your environment? How many environments do you have added to the Portainer server, how many containers are you running and what is the storage space free? The more details of your environment the better :) |
I'm having the same issue with the latest version (2.21.4), other version were perfectly fine. It just seems to hang randomly, no extreme resource usage, just unresponsive. |
2024-10-30.20-33-57.mp4Example of slowness, works as-expected and then randomly hangs. (This is via lan) |
for me, the problem was there since 2.21.1 and I was hoping updating will fix it, but it looks like it made it slightly worse. EDIT: the problem I have is similar to the one posted in the video from @jusvit. Most of the time even login screen loads forever, if i refresh it will load fast sometimes up to dashboard, then clicking stacks or containers or selecting the environment loads forever again. |
Correction, I didn't check each version, the issue was just recent since I updated. |
Hello, happy to do it, during the weekend. Will there be any sensitive info in the logs that I need to mask before uploading? |
Sorry for accidental closure, fat fingers.. |
@tomarigr No you should not find any sensitive information in these logs, it's always good to double check before sharing logs for sensitive information though |
Commenting to follow this as well. I'm having similar issues making it hard to access my dashboards over VPN sometimes :/ |
@AKASGaming Can you please share your Portainer environment details? |
I enabled debug logging, this was the logs during a slowdown: The slowdown was a good 15 seconds, the api/motd seems unrelated. |
hello, unfortunately didn't have the time to do the debug, just wanted to report that today, I had to reboot 18 times to get it to work fast again. Slowness amount seems to be random from reboot to reboot, from a few seconds, to not loading even after 5 minutes, then 1 more reboot and BAM, it's back working again. |
This really sounds similar to an issue I'm having, I'm thinking it's related to OAuth login somehow, since especially the login process takes ages, and sometimes randomly logs me out since the latest portainer version. (Business Edition 2.21.4). When I avoid OAuth and login through P.S. |
@jusvit Can you share the complete log? |
Hello, FYI I don't have 2FA and still get the slowness after reboot, but the root cause could be the same. @jusvit please also try rebooting a few times when 2FA enabled and see if you get a lucky boot where everything works perfect. |
Apologies folks, that's as far as I want to mess around diagnosing. I've already downgraded, hopefully you find the root cause. |
Before you start please confirm the following.
Problem Description
the web ui gets slow and unresponsive. A simple container action takes ages to load to the point where it's unusable anymore. This used to go away after a few restarts of the machine, I used to get a lucky boot where everything worked perfect. There is no excessive CPU/RAM/DISK load, everything is on idle and all other containers are fast and responsive.
Even focusing on an other tab and back to portainer tab triggers a slow load that might last 3-4 minutes.
Updated to latest
Expected Behavior
fast
Actual Behavior
slow
Steps to Reproduce
any action takes ages of loading.
Portainer logs or screenshots
please let me know what logs you need.
Portainer version
2.21.4
Portainer Edition
Community Edition (CE)
Platform and Version
Docker
OS and Architecture
Ubuntu 22.04 amd64
Browser
any
What command did you use to deploy Portainer?
Additional Information
No response
The text was updated successfully, but these errors were encountered: