What are you trying to accomplish?
a secure https connection between our vm and github. We have set it up to use port 443 and have it behind a reverse proxy using another vm running Apache. The webpage url of sonarqube to the ip it uses on its sever will use https thanks to the reverse proxy setup. But we are trying to work out how to prevent the FQDN of the server its self from also being available at the same time on the same port. It is a security vulnerability. Would adding another network port and under another IP is only solution I can work out but I wanted to see if there was a better solution.
Hi,
Welcome to the community!
If I understand correctly, you’ve successfully exposed
https://sonarqube.myco.com/sonar
And you’re trying to understand how to prevent
https://sonarqube.myco.com
from also being available?
Have you tried having the proxy block it?
Alternately, you could stop using a “context” for SonarQube and simply expose it at
https://sonarqube.myco.com
HTH,
Ann
Kind of. What I am trying to keep from being available is http://vmserver.mydomain.com from being the proxy routes https://sonarqube.mydomain.com/sonar as we want just fine.
Hi,
This is proxy configuration, and a bit out of scope for us.
Ann
Is there any advice you can offer?