mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-26 01:45:54 +03:00
[GH-ISSUE #107] Loading takes 10 seconds, extra config needed? #94
Labels
No labels
awaiting feedback
bug
cannot reproduce
dns provider request
duplicate
enhancement
enhancement
enhancement
good first issue
help wanted
invalid
need more info
no certbot plugin available
product-support
pull-request
question
stale
troll
upstream issue
v2
v2
v2
v3
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/nginx-proxy-manager-NginxProxyManager#94
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @sanderdatema on GitHub (Mar 24, 2019).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/107
When using Caddy my sites load pretty fast, but with NginxPM it takes about 10 seconds for each first load. After that it's ok. But when I wait a few minutes, it'll take a few seconds again.
Am I missing something?
@jc21 commented on GitHub (Mar 27, 2019):
The admin site isn't 100% optimised and it might be that it's JS assets aren't cached. Or it might be that the database isn't warm. Open your web browser's dev tools and see which parts (js or xhr) are taking the longest to respond.
@sanderdatema commented on GitHub (Mar 27, 2019):
The weird thing is that the first 10 seconds absolutely nothing happens. Only after that the browser is able to request anything. Like a dns request that takes ages. Except that it can't be that, because Caddy works fine.
It's not just your admin site, it's any site.
Is there a debug setting I could use?
@jc21 commented on GitHub (Mar 27, 2019):
If it is a DNS issue you can test by opening a console and trying to lookup a record and see how long it takes:
Try different domains you've probably never visited, to make sure you're not using your local dns cache.
@sanderdatema commented on GitHub (Mar 28, 2019):
But that's what I said: it's not a dns issue, Caddy would have trouble too, then.
Edit: somehow Wordpress caused this. Other sites did load fine. So, it's solved.
Thanks for taking the time to look into this.