Marker.io works on all cloud-based versions of GitLab. However, for self-hosted instances, it will work given two conditions.
Read the statements below and see how they apply to you:
"Our GitLab instance is set up on a local network"
Marker won't work in that use case.
If your GitLab instance is not accessible via a public DNS because it's installed on a private / local network, Marker.io will not be able to establish a connection. Typically, if you use a VPN to connect to your GitLab account, it is very likely that your GitLab account is set up on a private and local network, which unfortunately makes it impossible for Marker.io to access your GitLab account.
However if your GitLab instance is accessible via a public DNS, keep reading.
"Our GitLab instance is behind a corporate Firewall"
"What IP address do I add to my iptables in Linux?"
To make sure that Marker.io can go through your corporate Firewall, you will need to whitelist our servers using the following IP:
If your GitLab instance is publicly accessible and your firewall allows access to our servers, it will work.
If you need more information, please feel free to reach out via email at firstname.lastname@example.org or via our chat widget.