[GH-ISSUE #107] Loading takes 10 seconds, extra config needed? #94

Closed
opened 2026-02-26 05:34:28 +03:00 by kerem · 4 comments
Owner

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?

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?
kerem 2026-02-26 05:34:28 +03:00
Author
Owner

@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.

<!-- gh-comment-id:476968570 --> @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.
Author
Owner

@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?

<!-- gh-comment-id:477272699 --> @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?
Author
Owner

@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:

nslookup www.google.com.au

Try different domains you've probably never visited, to make sure you're not using your local dns cache.

<!-- gh-comment-id:477378683 --> @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: ``` nslookup www.google.com.au ``` Try different domains you've probably never visited, to make sure you're not using your local dns cache.
Author
Owner

@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.

<!-- gh-comment-id:477456988 --> @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.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/nginx-proxy-manager-NginxProxyManager#94
No description provided.