Argo config for one hostname several services?

Hello. Try as I might the only way I can connect to multiple services on the same host is with different hostnames. This makes running a Git server listening on 80,443, and 22 difficult. Is it not possible to have more than one service on a hostname?

I have tried named tunnel (running as a service) and tunnel id’s (As far as I understand that’s legacy).


  • hostname: mygit.server
    service: http://localhost:80
  • hostname: mygit.server
    service https://localhost:443
  • hostname: mygit.server
    service ssh://localhost:22
  • service https_status:404
    The first service was the only one matched even if I test the tunnel with ssh://mygit.server

I also tried.

I would really like to not have to use a separate hostname for each service.

At a minimum I would like to have http and https go to the correct service port without having to use a different host name. Is that possible?

Hello @erlarso1 ,

The right way is to assign different hostnames to each service as per the tutorial in

That’s how http-based proxying decides where to go next.

Is there a creative solution to having a web server that is running on 80 and 443 to be able to use Argo Tunnel without having to come up with a different hostname for each service?

I assume redirecting in the host won’t work. HSTS?

I’m not sure why you need Port 80 and 443. I only use 443 and take care of the redirects in the SSL/TLS → Edge Certificates section (Always Use HTTPS).

For 22, I create a subdomain ‘ssh’. Same server, and I adjust my SSH connections accordingly.

I can’t actually force HTTPS on that edge cert because it’s a san cert with 70 entries, some being stars. The domains encompass probably a thousand sites managed across many different groups. Some built a log long time ago in a dreamweaver product far far forgotten. I am currently looking for a way in the tunnel to handle redirecting 80

You can also use Page Rules to redirect http over to https

Thanks for the Page Rule. I created one for “Always HTTPS” and made a second hostname for the ssh config.

1 Like

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.