Trusted WordPress tutorials, when you need them most.
Beginner’s Guide to WordPress
Coppa WPB
25 Million+
Websites using our plugins
16+
Years of WordPress experience
3000+
WordPress tutorials
by experts

Come risolvere l’errore Troppi reindirizzamenti in WordPress

Nota editoriale: guadagniamo una commissione dai link dei partner su WPBeginner. Le commissioni non influenzano le opinioni o le valutazioni dei nostri redattori. Per saperne di più su Processo editoriale.

L’errore “Errore troppi reindirizzamenti” è un errore di WordPress che può essere causato da un plugin o da impostazioni errate. In effetti, è uno degli errori più comuni riscontrati dai nostri lettori e da altri utenti di WordPress.

Questo errore può persino bloccare l’accesso al sito web, rendendo la correzione un po’ complicata. Fortunatamente, abbiamo risolto il problema dei troppi reindirizzamenti più volte, quindi sappiamo esattamente cosa fare.

In questo articolo vi mostreremo come risolvere facilmente il problema “Errore di troppi reindirizzamenti” in WordPress. Inoltre, spiegheremo come ripristinare l’accesso al vostro sito web e come risolvere l’errore.

Fixing too many redirects error in WordPress

Suggerimento dell’esperto: Preferite lasciare la risoluzione dei problemi ai professionisti? I nostri servizi di assistenza WordPress sono in grado di correggere l’errore in pochissimo tempo e di far tornare il sito operativo. Inoltre, offriamo correzioni una tantum, così non dovrete preoccuparvi di contratti continui.

Cosa causa il problema “Errore di troppi reindirizzamenti” in WordPress?

L’errore “Troppi reindirizzamenti” è causato da un problema di reindirizzamento mal configurato in WordPress.

Come forse già sapete, WordPress dispone di una funzione di struttura degli URL SEO-friendly che utilizza la funzione di reindirizzamento. Allo stesso modo, molti popolari plugin di WordPress utilizzano questa funzione per impostare reindirizzamenti temporanei, creare reindirizzamenti 301 permanenti e correggere errori 404.

Se si utilizza un plugin per risolvere il problema del contenuto insicuro SSL o un plugin per la cache di WordPress, è possibile che influisca anche sui reindirizzamenti e causi l’errore “troppi reindirizzamenti”.

Ecco come appare il messaggio “ERR_TOO_MANY_REDIRECTS” in Google Chrome.

Error Too Many Redirects in Google Chrome

Tuttavia, questo errore non dice che cosa sta causando il conflitto e che sta forzando il ciclo di reindirizzamento in WordPress.

Ecco come si presenta l’errore in Firefox con il messaggio “La pagina non viene reindirizzata correttamente”.

Too many redirects error in Firefox

Detto questo, vediamo come risolvere il problema dei troppi reindirizzamenti in WordPress.

Vi guideremo passo dopo passo nella risoluzione dei problemi, nell’accesso al vostro sito WordPress e nell’evitare che l’errore si ripeta.

Video tutorial

Subscribe to WPBeginner

Se preferite le istruzioni scritte, continuate a leggere.

1. Cancellare i cookie e la cache del browser

Una causa comune dell’errore potrebbe essere rappresentata dai cookie del browser web. Provate ad accedere al sito web utilizzando un altro browser, come Firefox, Safari, Opera o Microsoft Edge.

Se si riesce ad accedere normalmente al sito web utilizzando un altro browser, è necessario cancellare i cookie del browser e la cache nel browser abituale.

Clear cookies and cache in Google chrome

Abbiamo una guida dettagliata su come cancellare la cache del browser in tutti i principali browser che vi aiuterà a farlo.

Se invece la modifica del browser non risolve il problema, si può passare alla fase successiva.

2. Disattivare tutti i plugin di WordPress

La causa più comune dei loop di reindirizzamento di WordPress o “ERR_TOO_MANY_REDIRECTS” è un conflitto di plugin. Un plugin di WordPress che tenta di impostare un reindirizzamento in modo tale da entrare in conflitto con i reindirizzamenti predefiniti di WordPress può causare questo messaggio di errore.

Per risolvere il problema, è necessario disattivare tutti i plugin di WordPress sul sito web. Normalmente, è sufficiente andare alla pagina Plugin ” Tutti i plugin nell’area di amministrazione di WordPress e disattivare i plugin da lì.

Deactivate all plugins

Tuttavia, supponiamo che a causa dell’errore di reindirizzamento non sia possibile accedere all’area di amministrazione di WordPress.

In questo caso, è necessario disattivare i plugin di WordPress utilizzando un client FTP come FileZilla o l’applicazione File Manager del pannello di controllo dell’hosting WordPress.

È sufficiente collegarsi al proprio sito web con un client FTP e accedere alla cartella /wp-content/.

Renaming the plugins folder using FTP

Qui troverete la cartella dei plugin, che dovrete rinominare in ‘plugins.deactivate’.

In questo modo si disattivano tutti i plugin di WordPress sul sito.

Renamed plugins folder

In pratica, WordPress cerca una cartella chiamata plugins per caricare i file dei plugin. Quando non trova la cartella, disattiva automaticamente i plugin attivi nel database.

Ora, potete provare a visitare il vostro sito web WordPress. Se ora siete in grado di accedere all’area di amministrazione di WordPress, significa che uno dei plugin ha causato l’errore.

Per capire quale sia il plugin colpevole, è necessario tornare al client FTP o all’applicazione File Manager e rinominare la cartella plugins.deactivate in ‘plugins’.

Dopodiché, passate all’area di amministrazione di WordPress del vostro sito web e andate alla pagina Plugin ” Tutti i plugin. Da qui, potete attivare i vostri plugin uno per uno e poi visitare il vostro sito web per vedere se riuscite a riprodurre l’errore.

Una volta individuato il plugin che causa l’errore, è possibile trovare un’alternativa a tale plugin o segnalare il problema al forum di supporto WordPress del plugin.

3. Correggere gli URL di WordPress

Un’altra causa importante di questo errore è una configurazione errata delle impostazioni URL di WordPress. Normalmente, è possibile visualizzare queste opzioni nella pagina Impostazioni ” Generali “.

WordPress URL settings

Per la maggior parte dei siti web, gli URL nei campi Indirizzo WordPress e Indirizzo sito devono essere uguali. Tuttavia, alcuni utenti possono ritrovarsi a utilizzare il suffisso “www” in un URL e un URL non www nell’altro.

Poiché potreste non avere accesso all’area di amministrazione di WordPress, potrebbe essere necessario correggere gli URL di WordPress utilizzando un client FTP o l’applicazione File Manager.

Collegatevi al vostro sito WordPress utilizzando un client FTP e andate a /wp-content/themes/your-theme-folder/.

Edit functions.php file

Da qui, è necessario trovare il file functions.php e modificarlo con un editor di testo semplice, come Notepad o TextEdit.

Successivamente, è necessario aggiungere il seguente codice in basso:

update_option( 'siteurl', 'https://example.com' );
update_option( 'home', 'https://example.com' );

Non dimenticate di sostituire “https://example.com” con gli URL del vostro sito. Ora è possibile salvare le modifiche e caricare il file sul proprio sito web.

Successivamente, provate a visitare il vostro sito web per vedere se l’errore si risolve.

Per ulteriori metodi, consultate il nostro tutorial su come modificare facilmente gli URL di WordPress.

4. Ripristinare il file .htaccess di WordPress

Il file .htaccess è un file speciale utilizzato dal server del sito web per gestire i reindirizzamenti e altre impostazioni del server. WordPress utilizza questo file anche per gli URL SEO-friendly e altri reindirizzamenti.

A volte, i plugin di WordPress possono apportare modifiche al file .htaccess del vostro sito web, innescando questo errore. È anche possibile che la disattivazione di un plugin non rimuova le modifiche dal file .htaccess.

In questo caso, è necessario reimpostare manualmente il file .htaccess di WordPress.

Anche in questo caso, dovrete accedere al vostro sito web utilizzando un client FTP o l’applicazione File Manager nel vostro cruscotto di hosting. Una volta collegati, vedrete il file .htaccess nella cartella principale del vostro sito web.

Editing .htaccess file via FTP

Nota: se non riuscite a trovare il vostro file .htaccess, consultate la nostra guida su come trovare il file .htaccess in WordPress.

Innanzitutto, è necessario scaricare una copia del file .htaccess sul computer come backup. Dopodiché, si può procedere all’eliminazione del file dal proprio sito web.

Ora potete provare a visitare il vostro blog WordPress. Se tutto funziona normalmente, significa che il file .htaccess ha causato l’errore di reindirizzamento.

Ora, poiché abbiamo cancellato il file .htaccess, è necessario ricrearlo. Normalmente, il vostro sito WordPress è in grado di farlo da solo. Per accertarsene, basta andare alla pagina Impostazioni ” Permalinks e fare clic sul pulsante “Salva modifiche” in basso.

Refresh permalinks to create .htaccess file

5. Prevenire l’errore Troppi reindirizzamenti in WordPress

Speriamo che i passaggi appena descritti abbiano risolto il problema del reindirizzamento sul vostro sito web. Se il problema non è stato risolto, potrebbe essere necessario parlare con la società di hosting di WordPress per assicurarsi che non ci sia un problema di server.

Una volta risolto il problema sul vostro sito, dovreste essere in grado di capire cosa lo ha causato.

Se si tratta di un plugin, è necessario segnalare il problema al forum di supporto del plugin. Consultate la nostra guida su come richiedere il supporto di WordPress. Tuttavia, se non riuscite a ottenere aiuto, potete sempre trovare un plugin alternativo che faccia la stessa cosa.

Se l’errore è stato causato da un’errata configurazione del sito WordPress, è possibile prenderne nota e assicurarsi che le impostazioni del sito siano configurate correttamente.

Per ulteriori suggerimenti, consultate il nostro tutorial dettagliato su come risolvere i problemi di WordPress da soli come un vero professionista di WordPress.

Speriamo che questo articolo vi abbia aiutato a correggere l’errore “troppi reindirizzamenti” sul vostro sito web. Potreste anche voler mettere tra i preferiti il nostro manuale definitivo degli errori comuni di WordPress e vedere come contattare l’assistenza WordPress.

Se questo articolo vi è piaciuto, iscrivetevi al nostro canale YouTube per le esercitazioni video su WordPress. Potete trovarci anche su Twitter e Facebook.

Divulgazione: I nostri contenuti sono sostenuti dai lettori. Ciò significa che se cliccate su alcuni dei nostri link, potremmo guadagnare una commissione. Vedi come WPBeginner è finanziato , perché è importante e come puoi sostenerci. Ecco il nostro processo editoriale .

Avatar

Editorial Staff at WPBeginner is a team of WordPress experts led by Syed Balkhi with over 16 years of experience in WordPress, Web Hosting, eCommerce, SEO, and Marketing. Started in 2009, WPBeginner is now the largest free WordPress resource site in the industry and is often referred to as the Wikipedia for WordPress.

Il kit di strumenti WordPress definitivo

Ottenete l'accesso gratuito al nostro kit di strumenti - una raccolta di prodotti e risorse relative a WordPress che ogni professionista dovrebbe avere!

Reader Interactions

303 commentiLascia una risposta

  1. Syed Balkhi says

    Hey WPBeginner readers,
    Did you know you can win exciting prizes by commenting on WPBeginner?
    Every month, our top blog commenters will win HUGE rewards, including premium WordPress plugin licenses and cash prizes.
    You can get more details about the contest from here.
    Start sharing your thoughts below to stand a chance to win!

  2. David Najman says

    Hi,
    I had this error on the product tag page. I tried all the possible repairs mantioned above with no luck.
    Finally, I had to rename slug for tags not to be numbers, eg. 2016, so I renamed it to r2016 and it started to work!
    It must have been caused by some wordpress update, because it have been working few years before with tags named as numbers.

    • WPBeginner Support says

      Thanks for sharing what worked for you, if your product page is created by a plugin you may want to try reaching out to the plugin’s support to let them know about that issue

      Admin

  3. Yavan Kumar says

    Hi,

    My whole website is running properly, but the homepage is redirected too many times and same issue with the wp-admin page too. I tried all the methods you mentioned but nothing worked for me.

    Please advice me if there is any another solution for that.

    Thanks in advance…

    • WPBeginner Support says

      If none of the methods from the article worked, you would want to reach out to your hosting provider for them to see if there are any issues they can see on their end.

      Admin

  4. John Zoetebier says

    My web site is a Bitnami WordPress deployment on Google Cloud Platform.

    When I use:
    define(‘WP_SITEURL’, ‘http:/example.cloud’);

    the home page gets redirected to itself and browsers error message.
    I now use the original Bitnami setting and it works great !
    define(‘WP_SITEURL’, ‘http://’ . $_SERVER[‘HTTP_HOST’] . ‘/’);

    • WPBeginner Support says

      You are missing a slash next to your http in the first define statement but thank you for sharing your workaround.

      Admin

  5. Chad says

    I had to desactivate a plugin and it worked back fine. I identified the plugin to desactivate by looking into my URL where I was getting a redirect error. The plugin name was written there.

  6. Josh says

    I’ve tried all the steps here with no luck today. Luckily my website is functioning ok but I can’t log into the wp-admin dashboard for anything.

    What are the other options? There must be other ways I can figure out what’s causing it?

    • Deby says

      I’m having the same. My site works fine for visitors, but I only get the redirect error for the backend, my WP dashboard.
      It’s a new site and I don’t even have any plugins installed yet. I’m stumped.

  7. Bryant Thomas says

    Holy Cow That worked, I’ve done many websites migrations and never ran into this issue. Thank you the define(‘WP_HOME’,’http://example.com’);
    define(‘WP_SITEURL’,’http://example.com’); worked with the www.

  8. Rutvi Trivedi says

    Hi, My problem is when I go to my site’s dashboard(/wp-admin) it is giving me this error I tried this solution and unfortunately it is not working. Please help me to solve this error.

  9. Shakeane says

    I just want to say thank you so much for sharing this knowledge, you wouldn’t understand how much this has helped me, something as minor is adding www or leaving the forward slash at the end has caused so many headaches, thank you so much.

  10. hassan says

    dear sir,
    i have huge data on my website i change my address directly from http://www.example.com to example.com i remove www from wp-confiq and phpmyadmin without doing the above procedure, now i update all the plugin and theme everything is fine but my theme setting is not editing when i am going to change setting of my theme the changes reverting …please help how to solve this problem i will be thankful to you
    i am trying to solve this problem from three days but fail
    please help

  11. Sachin says

    Hi, my website is running without any error but i have this issue in backend when i open appearance>customize tab. I am unable to customize my website from backend. How can i solve it?

  12. Toheeb says

    Hi!

    Thank you for your post…

    I was able to solve mine changing the WP_SITEURL and WP_HOME to lowercase letters. I capitalized each word formerly for readability and as it turned out, it redirects post paginated pages.

    Everything seems fine now. Thank You

  13. Rudy Reteig says

    I made a redirect in ADDOn Domain to rid my site of a tail, “/blog”, behind my URL, appeared when launched the site. This was in my opinion automatically done, as I have two sites on the same PUBLIC_html directory. probably to avoid conflict of files with the same name of the two sites

  14. Robin says

    None of these fixes worked for me. In the end it turns out I had setup a custom page rule in CloudFlare a long time ago to treat the wordpress dashboard different to the rest of the site. It had “SSL – Flexible” set which causes the error. I just set the rule to “Full” and it works fine again.

  15. Florian says

    I also had the problem, so I started searching for a solution and found out that the CDN was causing that error. I switched it off and it worked again

    • Jennifer says

      Thank God I saw your reply. I thought because I had added the Yoast SEO plugin, it was causing the issues, but I had also activated CDN in my control panel and that was the problem!

  16. Alex Jr says

    I deactivated all plugins, disabled the current theme, deleted .htaccess, but I’m still getting the “too many redirects” error when I try to access my wordpress site. What is causing it and how can I fix it?

  17. Dan says

    Just had this happen to me on a new site I’m working on. The issue turned out that I created my child theme with spaces in the name. As soon as I renamed the child theme folder to my-child-theme it worked. I did have to go and make my child theme active again to make it work right. Hope this saves someone so grief and aggravation!

    • ANA says

      Dan, I just wanted to say THANK YOU!!!!!!!
      That was my problem too, apparently. I changed the name and folder to include a dash and everything works fine.

  18. Santiago says

    I’m finding that when I try to set my Permalink to Post Name I get the redirect issue. When I set it to Plain, no issues. I’ve disabled all the plugins and still the same thing.

    I’m new to WP but 20+ years IT, any help would be greatly appreciated.

  19. Damion says

    +1 on this and thank for for so thoroughly and generously sharing your knowledge – you saved me hours of work today.

  20. Bilal Asghar says

    This is a really helpful article. I had the redirection issues with my WordPress website. I just changed my Post URLS going to Setting>Permalinks.

  21. Ebad Ur Rehman says

    My site is redirected too many time in the preview of customization
    other functions of theme are working fine.
    please tell the solution for the problem

  22. Sharon Booker says

    Thank you so much. I called my hosting service help desk twice and nothing they told me to do helped. This fixed the error.

  23. Amit Khandelwal says

    I’m getting “ERR_TOO_MANY_REDIRECTS” problem only on website Home page but other pages working fine. I think plugin “Redirection” create this problem but it’s my need to keep activate this.
    Please suggest.

  24. Tenzin Nima says

    Thank you so much!! I have been looking for solution for whole day and finally solved it.

    Thank you

  25. maria says

    ive tried the first option, Settings » General and changed the url. the thing is, i accidentally put a ; instead of a . on the adress.
    Now the site is all messed up and i cant even login on the admin user anymore, to change it back :/ any tips?

  26. Em Walker says

    Hi, Every time I go to the WIDGET page to load my adsense ads then my page freezes up and becomes unresponsive, how can I fix this, please

  27. Abiskar Bharati says

    I tried all the things mentioned in the blog but issue still persisted so I did what Jake Philips(one of the comment above) did and I found that something had changed the permalink structure setting to:
    /’/%year%/%monthnum%/%day%/%postname%/’

    I changed it back to (as the comment suggests) :
    /%year%/%monthnum%/%day%/%postname%/

    and then everything was working fine again…

  28. Cindy says

    When I put my link on Facebook my photo that’s on my webpage does not come up just my website name and URL. Any idea what I need to do to have a thumbnail photo?

    • Felix says

      Hi, CINDY.
      That’s because you didn’t use Yoast plugin, and didn’t set the rules on Facebook tab. The issue is related to open graph protocol.

  29. Khori Carnes says

    Hi. I am having a some what odd issue, i feel. My redirect issue is that when i attempt to access my wordpress admin page using my domain, it redirects me to godaddy.com. my only explanation I can come up with is that i purchased my domain name from godaddy. However i purchased my web hosting from hostgator. Regardless, i can not access my admin page for wordpress to begin establishing my new website.

    Any and all help or suggestions would be greatly appreciated! Thanks

    • WPBeginner Support says

      Hi Khori,

      You can contact GoDaddy support and they can help you point out your domain name to your hosting provider. All you need to do is go to your GoDaddy account and point Name Server settings for your domain name to HostGator.

      Admin

  30. Ralf says

    In my case the problem was special characters in the URL. You can’t have those with wordpress. E.g. German umlauts: ÄÖÜ – need to be converted.

    • Teemu says

      Yes and no. I succesfully ran a website with “ä” character in there for a few years. But this time this might be the reason why I’m searching help to this problem here with a website that now has the same “ä” character there also…

  31. Don Stewart says

    I panicked when I could not access my website home screen (though I could the other pages). I messed around with the Settings=>General URL settings, and I saw that the same address appeared as the WordPress URL and the website URL—which meant it was going around in circles, as you pointed out. I fiddled with that for awhile, almost locking myself out of WordPress altogether, but then deactivated several recently installed plugins. Fixed! I’m not sure which plugin caused it—I will investigate that, by omitting the one I think is most likely and one-by-one reactivating the others, but my suggestion is to follow your article from the bottom up. Check out those recent plugins!

  32. Jake Phillips says

    I had just enabled CDN and SSL in Bluehost for my WordPress site when this started happening. I found that something had changed the permalink structure setting to:
    /’/%year%/%monthnum%/%day%/%postname%/’
    I changed it back to:
    /%year%/%monthnum%/%day%/%postname%/
    and then everything was working fine again…

  33. Asma says

    Hi,
    Your article is really good and may be a solution of my recent problem. But I am not a WordPress expert and not enough brave to experiment with my site, though the blog is completely built by myself.

    However, I’m seeing the following things from last two days–

    “This page isn’t working
    m redirected you too many times.
    Try clearing your cookies.
    ERR_TOO_MANY_REDIRECTS”

    I’ve tried many times after clearing cookies, still, I can’t log into my site.

    Can you please give a solution?

  34. Adeshola says

    My problem seemed to be a mixture of plugins and wp-config.php. After deactivating my plugins, I was able to access my site but not my wp-admin area. I fixed this by updating my wp-config with the codes provided above. However, they worked only after I put them before the “/* That’s all, stop editing! Happy blogging. */” line. This was something you guys didn’t include in your tutorial but I found somewhere else. So thanks for everything. My site works now.

  35. George says

    Just wanted to say this article helped me a great deal… Here’s my case:

    WP installed in a directory: domain.com/widget

    domain.com .htaccess edited for SEO purposes to say
    DirectoryIndex /widget/index.php /widget/

    This caused the “too many redirects” issue. Possibly because of the trailing slash in the domain.com .htaccess file??

    Anyway, this fixed it:

    domain.com .htaccess edited to:
    DirectoryIndex /widget

    Now it works.

    Huzzay for cPanel!!!

  36. Mirjam says

    My issue is that trying to access the login page keeps giving me a redirect to https:// but my site is in http://. Have tried everything, adding home url to config.php, disabling plugins, renewing .htaccess. There is no redirect defined in CPanel so I’m lost as to why this is happening. The site is available, but I cannot access admin.

    Getting a bit hopeless here…

  37. Gilbert Stawny says

    If none of the above works, rename your .htaccess file to htaccess.old or something. Try to log in again.

  38. Talha Wahid says

    Thanks a lot, Finally i solve it by spending whole week. only adding to the wp-config.com
    define(‘WP_HOME’,’http://example.com’);
    define(‘WP_SITEURL’,’http://example.com’);

  39. Adrian says

    One way that you can create the infinite redirect loop is to set WordPress Address and Site Address using camel case, MyExampleWebsite.com for example . The domain part of a URI is supposed to be case-insensitive, the file part has to be case sensitive to cope with case-sensitive file systems. WordPress breaks if you use camel-case.

  40. Adnane says

    I had the same problem, solved it by going to cpanel then look in the security tab if there is mod security , if yes deactivate it.

    That was it for me.

  41. Howard Bussey says

    Thank you for writing this. I set up redirection with Easy HTTPS Redirection, and ran into the “too many redirections” problem. I solved it by turning off a property in Woo Commerce. In the checkout settings, I had both “force secure checkout” and “force HTTP when leaving the checkout” selected. I unselected the “force HTTP when leaving the checkout”, and no longer see the “too many redirections” problem. I didn’t have to edit any .htaccess file.

  42. Asser says

    If the issue is happening only when accessing the admin control panel , then look at the wp-admin and check if there is htaccess file in place (www/wp-admin/.htaccess ) and if you find one then rename it and refresh the admin URL (example.com/wp-admin/) and it should work .

  43. Akash Gadiya says

    Hi, I’ve tried all the troubleshooting options here but nothing seems to work. The last thing I remember doing was to take a full backup using the Backup Wizard on the cPanel. Could that in any way lead to this error (Too many redirects)

    Here’s a list of what I’ve done so far to fix this issue:
    1) Removed the backup file from the root directory
    2) Edited the wp-config file by adding those 2 lines of code, both with and without www
    3) Deleted the .htaccess files from the root directory and wp-content folder one at a time
    4) Scanned through all the comments to see if there is any possible solution, to no avail

    I have sought for the help of the root admin, hopefully we’d be able to fix this ASAP. If you think I’ve missed out on anything or could try anything apart from these, please do let me know.

    Thanks
    Akash

    • Akash Gadiy says

      I could finally fix the problem. It had something to do with the backend I guess. My admin reset the server and that breathed life into my website again. Thanks for this post though. Good luck to all trying to fix this problem. May the force be with you ;)

Lascia una risposta

Grazie per aver scelto di lasciare un commento. Tenga presente che tutti i commenti sono moderati in base alle nostre politica dei commenti e il suo indirizzo e-mail NON sarà pubblicato. Si prega di NON utilizzare parole chiave nel campo del nome. Avremo una conversazione personale e significativa.