Hello Raj:
I’m having a similar problem. It’s that I’ve built sonarqube and gitlab on my VM now, and then proxied the IP via nigin with 172.16.100.13 to proxy 172.16.110.210, and now my page is accessing sonarqube and gitlab via 172.16.100.13, but after I configure sonarqube After logging in with the gitlab account, I found that I couldn’t log in successfully. Then I switched IPs and tried to configure it via 172.16.110.210, and he was able to jump to soanrqube by logging in with a gitlab account. i want to know why the public 172.16.100.13 doesn’t work (i’m http requesting)。
I have found a GET request and the resources for this request feel wrong:
http://172.16.100.13:9000/oauth2/callback/gitlab. This is the configuration of the application, and when sonarqube logs in through gitlab and triggers this callback function, it is supposed to fetch sonarqube’s data resources, but now I am inexplicably jumping to gitlab
sonarqube8.9、gitlab15.0.1