I’m doing some testing of the Gitlab.com Pages feature and have enabled it on my repo. The URL I’ve been given https://my-project.gitlab.io/repo/ has unfortunately found its way on to Google’s Safe Browsing system and has been classified as unsafe.
This is rather unfortunate as one of my testers had enabled Safe Web browsing in Chrome and they now get a big red alert when attempting to access the URL. I didn’t see it because I do not have Safe browsing enabled.
The repo contains Hugo + Docsy (theme) with three markdown pages - pretty small, so i’m unsure why Google has classifed it as unsafe. Not to mention that Gitlab Pages are hosted on Google Cloud Platform… The project was only created yesterday, so it is new and could be a reason why Google is classifying it as unsafe.
I’m on a 30 day ultimate trial, and haven’t paid anything. I have entered a support ticket but as I am not a paying customer I doubt I will get a response. Does anyone have any tips?
thanks.
You could get a custom domain, and configure GitLab pages to use that domain. GitLab Pages custom domains | GitLab This requires DNS records for setup and verification, and includes that GitLab Pages will fetch a Lets Encrypt TLS certificate.
I’m using that setup for 3 domains, for example https://opsindev.news - served via Michael Friedrich / opsindev.news · GitLab
1 Like
Thanks yes, that’s the next option. I’m just wondering why/how this has got on this list and how to get it off…! I guess the IP address associated with this may have been compromised in the past, or the project name has been used before (although I doubt it) and was malicious.
Since the gitlab.io is a domain where anyone using Free GitLab.com can put anything, even malicious I wouldn’t be surprised there was some malicious usage in the past… sad really, but that’s what some people do.
Yes, sad :(. What’s strange is that “my_project.gitlabs.io” is not listed, but “my_project.gitlabs.io/repo” is…
Can you share the web URL and repository URL to get a better idea of what could be a problem?
