I believe the built in NGINX server may be the cause of thatIf you visit the webserver locally by its IP does it respond with the proper page?
Yes I do get routed to the correct page and when I ran the cURL command I did see it was redirecting to the sign-in page but with 302 status code. Please see the command output below.curl 10.10.10.30:10080 <html><body>You are being <a href="http://10.10.10.30:10080/users/sign_in">redirected</a>.</body></html> curl -I 10.10.10.30:10080 HTTP/1.1 302 Found Server: nginx Date: Sat, 17 Apr 2021 05:57:58 GMT Content-Type: text/html; charset=utf-8 Connection: keep-alive Cache-Control: no-cache Location: http://10.10.10.30:10080/users/sign_in Set-Cookie: experimentation_subject_id=eyJfcmFpbHMiOnsibWVzc2FnZSI6IklqWmhPVFV5WmpKbUxXRTNPVFV0TkdVNVppMWhZMlpqTFRSalpqRmhaV1JqTmpaak1TST0iLCJleHAiOm51bGwsInB1ciI6ImNvb2tpZS5leHBlcmltZW50YXRpb25fc3ViamVjdF9pZCJ9fQ%3D%3D--1e52d67fefb6115c51916e512ee89e72134ea6ab; path=/; expires=Wed, 17 Apr 2041 05:57:58 GMT; HttpOnly X-Content-Type-Options: nosniff X-Download-Options: noopen X-Frame-Options: DENY X-Gitlab-Feature-Category: projects X-Permitted-Cross-Domain-Policies: none X-Request-Id: 01F3F6GGKSQNK1DQZBJV8FJZNA X-Runtime: 0.090303 X-Ua-Compatible: IE=edge X-Xss-Protection: 1; mode=block Strict-Transport-Security: max-age=31536000 Referrer-Policy: strict-origin-when-cross-origin
I realize that my setup maybe not be an ideal one but I think this workaround will have to do since this is a home-lab environment of Gitlab running on a docker container. I had just wanted to get some understanding of what might have been happening in the background. I really appreciate your time @PiBa.