No longer possible to add CNAME records to Spectrum
What are the steps to reproduce the issue?
As my best understanding of the existing post and documents describing spectrum as a stable reverse proxy service. I think it evolves creating a cloudflare Cloudflare Tunnel connect my server to cloudflare network, then setting up a CNAME redirection from Spectrum to the tunnel address. However, I don’t see a option to use CNAME when creating a Spectrum service.
Or is there another way to do reverse tunneling in Spectrum.
May I ask if you’ve tried using cloudflared tunnel, if it suits your case, or rather Spectrum is what you need for your service to be running?
I am afraid you cannot add tunnel and then Spectrum over it.
You don’t have to create any tunnel nor install anything if you’re using Spectrum with desired port for your application or service.
Furthermore, if interested, you can try out cloudflared tunnel (maybe you don’t have to pay the Spectrum for such case?) and still protect your CNAME hostname with your WAF Custom Rules and other security options, as well as with Zero Trust and Access policy to restrict who can enter in.
If interested to try out at least, please see below:
Hi, yes, I have used cloudflared tunnel in a production fashion. But since it requires cloudflared.exe to be present to connect, it doesn’t fit my use case. The scenario is that is my server is behind a firewall with no public IP. How can one use Spectrum to expose a ssh service to public.
You can run it in the background as a service. At least I do. Closed port on the firewall, no access from internal network devices since Access policy is applied via Zero Trust, and using a public hostname including Browser rendered SSH, VNC and RDP depending on the need.
I am sorry to hear that.
Did you tried to setup DynamicDNS if possible for you?
