I appreciate the reply but need to clarify some of the questions and suggestions.
Domain is pointed to Cloudflare right?
gitlab is already setup and configured for https and ssh witch works from anywhere including the client server I am attempting to register
Cloudflare IP addresses are allowed to connect to 80 and 443?
sorry I don’t understand the context of this question. The only cloudflare IP’s I have had to configure are DNS. I don’t know of any others. The gitlab server DNS is configured in Cloudflare DNS and the server is listenting on 443 and 22 as per the guide listed on Cloudflares site “Zero Trust GitLab SSH & HTTP”
Are ports at the origins openned?
Are you referring to the client for the gitlab-runner outgoing ports? not sure why they would be blocked and can ssh to the gitlab server, from the runner client as well curl on 443.
You are sure you have got SSL certificate generated?
referring to the gitlab server? yes it has https cert issued by Cloudflare. It is on Flexible but will switch to FULL.
Hm, have you tried to run with debug? Do you get anything else?
yes I outlined that above and posted the results, not a lot to go on.
Maybe, hm, using the https address of Gitlab while registering it would help with it?
tried that with http and --debug
Dialing: tcp gitlab.myserver.com:80 ...
Dialing: tcp gitlab.myserver.com:443 ...
Dialing: tcp myserver.cloudflareaccess.com:443 ...
ERROR: Registering runner... failed runner=Bhz9nQKY status=200 OK
PANIC: Failed to register the runner. You may be having network problems.
Or, which version of Gitlab runner are you running?
Moreover, SSH and other stuff is working correctly?
Yes both tested no issues and I can ssh from the client server to gitlab but not run gitlab-register
Due to being proxied, could you try to remove the proxy config (http_proxy, https_proxy, ftp_proxy, socks_proxy) from /etc/environment file?
there is no proxy config.