Skip to main content
Super User

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

7
  • The GET /-/metrics is purely internal to gitlab. None of your requests from browser are actually reaching gitlab. The 500 error is served by the webserver you configured with plesk. The info your looking for will probably be in the webserver's error log. I don't use plesk at all but this might help: websavers.ca/view-web-server-logs-plesk
    – Zeitounator
    Commented May 27, 2019 at 12:29
  • Thank you. I do believe the requests are reaching GitLab because the line shows up precisely and exactly once for every time I make a browser request. The 500 error is also GitLab specific (With a GitLab logo, and the message "Please contact your GitLab administrator if this problem persists.") Checking the logs, there is two errors 500 for each request in my Plesk interface: GET / HTTP/1.0 and GET /favicon.ico HTTP/1.0 are the respective messages. I'm not sure how to get further info.
    – xerox102
    Commented May 27, 2019 at 12:55
  • You should edit your question and add those pieces of information there. In this case, you might get some relevant info in /var/log/gitlab/gitlab-workhorse/current
    – Zeitounator
    Commented May 27, 2019 at 13:05
  • Thanks. I've checked the specific logfile and found two error messages that pop up on startup (see edit), but checking on google, the specific situations don't really seem to apply to my configuration since I didn't actually change the default values of the redis configuration to begin with. I've also checked to see that both the workhorse and unicorn are listening on their ports (8080 and 8181), which they are
    – xerox102
    Commented May 27, 2019 at 13:28
  • Did you check that all gitlab services are up and running ? (gitlab-ctl status)
    – Zeitounator
    Commented May 27, 2019 at 13:38