You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Today I upgraded to 2.11.3 and also renewed my Lets Encrypt cert. I now get 522 errors from Cloudflare indicating that it can get through to NPM but it is not routing through to the proxy host.
The docker logs look fine, I can login to the web interface fine and everything looks good there.
However, the logs (both access and error) for all proxy hosts in /data/logs are size 0 bytes.
fallback_error.log is being written to fine so I know the process has write access.
The proxy host itself is accessible fine on my LAN.
Everything was working prior to upgrading the docker image and renewing the cert (this completed fine)
The individual proxy host logs were my only hope to troubleshoot why NPM does not seem to be contacting the host. Any ideas please?!
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Today I upgraded to 2.11.3 and also renewed my Lets Encrypt cert. I now get 522 errors from Cloudflare indicating that it can get through to NPM but it is not routing through to the proxy host.
The docker logs look fine, I can login to the web interface fine and everything looks good there.
However, the logs (both access and error) for all proxy hosts in /data/logs are size 0 bytes.
fallback_error.log is being written to fine so I know the process has write access.
The proxy host itself is accessible fine on my LAN.
Everything was working prior to upgrading the docker image and renewing the cert (this completed fine)
The individual proxy host logs were my only hope to troubleshoot why NPM does not seem to be contacting the host. Any ideas please?!
Beta Was this translation helpful? Give feedback.
All reactions