Replies: 2 comments
-
I don´t know but maybe you can increase logging https://github.com/verdaccio/verdaccio/wiki/Debugging-Verdaccio#debugging-with-debug and see if you get more info |
Beta Was this translation helpful? Give feedback.
-
Hey, I'm colleague of @Lasto13, so, we increased logging level and monitored situation and this is observation. We have Reverse Proxy LoadBalancer in front of Verdaccio, It was doing health check request every X seconds. This health check does not include "host" header - DNS record npm.the_company.com As loadbalancer is doing frequent requests (without host header) it is therefore likely to hit just on cache invalidation and render is done for loadbalancer health check (without host header), rendered page is therefore cached with IP instead of domain name like in original post ( What is candidate for Issue is that it was rendering with IP despite we had configuration set with
How did we fix it?
Logs:
This is request on cache invalidation
|
Beta Was this translation helpful? Give feedback.
-
Hello,
Verdaccio
latest:5.22.1
is deployed at EC2 with private IP 10.32.11.100, we have loadbalancer configured with certificates at https://npm.the_company.com/.After it is started it returns index.html with basename like:
<base href="https://npm.the_company.com/">
but after cca one hour it starts to serve a different index.html
<base href="http://10.32.11.100/">
Thus browser is rightfully complaining about mixed content.
Verdaccio itself is configured with compose like this:
and config.yml
After we start it we receive following index.html
And this is after one cca hour
Beta Was this translation helpful? Give feedback.
All reactions