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
If node[:nexus][:context_path] is set to "/" instead of the default "/nexus" I would expect https://localhost/ to hit nexus. Instead you get a Jetty error page:
HTTP ERROR: 404
Problem accessing /. Reason:
Not Found
Powered by Jetty://
In the nginx conf if I change proxy_pass http://127.0.0.1:8081/; to proxy_pass http://127.0.0.1:8081/nexus; then it works as I would expect. So I think it's just a matter of incorporating node[:nexus][:context_path] into the nginx conf.
The text was updated successfully, but these errors were encountered:
It seems to work as expected after a vagrant destroy && vagrant up. I think the issue is with trying to change the context_path in a subsequent convergence.
@KAllan357 I think it's because the nexus service isn't being restarted when nexus.properties changes. I can't figure out how to get it to do that though using either notifies on the template resource or subscribes on the service resource. Any ideas?
If
node[:nexus][:context_path]
is set to "/" instead of the default "/nexus" I would expect https://localhost/ to hit nexus. Instead you get a Jetty error page:Instead you have to go to https://localhost/nexus for it to work.
In the nginx conf if I change
proxy_pass http://127.0.0.1:8081/;
toproxy_pass http://127.0.0.1:8081/nexus;
then it works as I would expect. So I think it's just a matter of incorporatingnode[:nexus][:context_path]
into the nginx conf.The text was updated successfully, but these errors were encountered: