Worker redirect loop even after service is destroyed

Hi community,

I have the following problem that I am receiving a too many redirects error due to a worker redirect loop even after I destroyed the entire worker service.

Background
Two days ago I created a test worker for https://magicalnightsky.ch in order to redirect users based on their IP address to a local server based on a code example from the Worker’s library.

During the setup process I mistakenly added a route for my main store *.magicalnightsky.com/* for this worker. After I mistakenly created the route I deleted the the route shortly afterwards. I also like to mention that once I deployed the initial Worker I received an error in the Cloudflare dashboard when navigating to the Cloudflare > Workers > my-worker > Deployments tab. Forcing me to refresh the entire CF page.

After that, I actually destroyed the entire Worker service.
Apart from that, I did not change any other CF, DNS or server settings.

Current Problem
Now I am having the issue that Google, PayPal and all kind of services are having issues to connect to my main store domain which let to massive losses already in regard to sales.

As of now my website is available again from the EU and other countries, however if I connect to the US via VPN, I am receiving the too many redirect error. I also did a HTTPS Lookup with mxtoolbox and it shows the same error.

Questions

  • What could be issues for the too many redirects?
  • Could it be that the Worker was not fully destroyed?
  • How to stop the redirects?

Any help is highly appreciated to get my store back up and running.

Best,
Den

I’m going to guess it’s this. I have a slightly similar problem in that I deleted a domain, but left its worker route. Now I can’t delete the worker or the route.

I suggest you open a ticket and then post the ticket # here so we can escalate.

I’m going to guess it’s this. I have a slightly similar problem in that I deleted a domain, but left its worker route. Now I can’t delete the worker or the route.

Interesting, I believe there are some

I suggest you open a ticket and then post the ticket # here so we can escalate.

I have created a ticket #2349192 referring to this post. I hope that this can be resolved soon.

@denza I am currently investigating the issue on the ticket now. I will re-open the ticket and respond shortly. Lets continue the conversation on the ticket.

1 Like

I am currently investigating the issue on the ticket now. I will re-open the ticket and respond shortly. Lets continue the conversation on the ticket.

Awesome, thank you so much for looking into this. I will wait for your response to the ticket.

1 Like