Can't Access "SSL/TSL" Section of the Dashboard

General Dashboard
1

What is the name of the domain?

Can’t Access “SSL/TSL” Section of the Dashboard

What is the issue you’re encountering

(SSL/TSL (dash.cloudflare), endlessing loading problem on the dashboard)

What steps have you taken to resolve the issue?

  1. Tried hard refreshing the page.

What are the steps to reproduce the issue?

Posting this here in case anyone else might have this issue.

Page would try to load, and then give the tell the issue text box. When I pressed FN+F5, it would show the dashboard for a milisecond and then hang, and go immediately to the text box again. Did a lot of debugging on my end and then in the browser.

After noticing that the SSL/TLS encryption recommender was set to “auto,” and seeing some React errors in the logs, I suspected the automatic mode might be causing the hang. I used the Cloudflare API to change the ssl_automatic_mode from “auto” to “custom”.

Once I made this change, the SSL/TLS page on the Cloudflare dashboard loaded successfully, resolving the issue that had been plaguing me all weekend. I could finally access and manage the SSL/TLS settings for the problematic zone. The change I made through the API allowed me to regain control over the dashboard and confirmed that the automatic SSL/TLS configuration was the root cause of the issue.

2

May I ask if you’ve tried to logout and log back into the Cloudflare dashboard? :thinking:

Possibly, you’d need to clear all the cache and cookies to fix it, or try by using a different Web browser.

Happy to hear this!

My best guess, there could be something “in the air” if the Cloudflare API was in process of updating or changing in the background, which would have such impact on the Cloudflare dashboard itself :thinking:

3

Ah! That’s an important step I forgot to include.

I did log out / log in, tried refreshing and quite a bit of other steps before I ended up using cURL to set that the custom (it was set to auto).

Even tried accessing it on mobile to see if it could be my laptop but the problem was still the same. But the only action that ended up fixing the issue on my end was changing it via cURL.

4

This topic was automatically closed after 15 days. New replies are no longer allowed.