search

NginxProxyManager / nginx-proxy-manager

Docker container for managing Nginx proxy hosts with a simple, powerful interface
https://nginxproxymanager.com
MIT License
20.96k stars 2.42k forks source link

Some Proxy Hosts Have No logs #2094

Open whoshoe opened 2 years ago

whoshoe commented 2 years ago

Hi,

I have 7 proxies set up in NPM with only 2 disabled. That leaves me 5 proxies in use but in the log folder it only has files for 4 of the proxies. Among those files only 2 proxies have actual log entries.

So the 5 services are 2 PhotoPrism, Guacamole, Bookstack and Ghost. Only 1 Photoprism instance and Bookstack have actual content in the access log.

NPM is running in docker (jlesage/nginx-proxy-manager) version v1.26.1

Positivelight775 commented 2 years ago

Insert stay now... Bluetooth wifi...

On Sun, Jun 5, 2022, 2:27 AM HT @.***> wrote:

Hi,

I have 7 proxies set up in NPM with only 2 disabled. That leaves me 5 proxies in use but in the log folder it only has files for 4 of the proxies. Among those files only 2 proxies have actual log entries.

So the 5 services are 2 PhotoPrism, Guacamole, Bookstack and Ghost. Only 1 Photoprism instance and Bookstack have actual content in the access log.

NPM is running in docker (jlesage/nginx-proxy-manager) version v1.26.1 https://hub.docker.com/layers/nginx-proxy-manager/jlesage/nginx-proxy-manager/v1.26.1/images/sha256-884cb243f4372cbfcd1d1ee4979b362e9f6126e98feb7d36e121a1b5248a973f?context=explore

— Reply to this email directly, view it on GitHub https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2094, or unsubscribe https://github.com/notifications/unsubscribe-auth/AVMDK3X7IOGKEROLI2OPQT3VNRXGPANCNFSM5X4Y4V7A . You are receiving this because you are subscribed to this thread.Message ID: @.***>

the1ts commented 2 years ago

Since you aren't using jc21's docker image, perhaps you should ask in jselage's github also.

But there are many reasons that you think nginx isn't logging but is somewhere you aren't finding it.

  1. Is buffering turned on? it will mean there may be a very large lag between website hit and writing logs. Check the proxy_host/*.conf files for access_log section
  2. If the app uses websockets, the majority of the hits will not appear in access logs and I don't think NPM sets up websocket logging.
  3. Access log names have changed over time, make sure by checking the filesystem. Old and new sites can write as different naming styles.
  4. Check the /data/nginx/proxy_host/*.conf files and check where they are being written to, perhaps the location has changed.
  5. Is this an issue with docker/host filesystem syncing? Check both inside the docker (using docker exec) and on the docker host.
github-actions[bot] commented 5 months ago

Issue is now considered stale. If you want to keep it open, please comment :+1: