Support » Plugin: WP Force SSL & HTTPS SSL Redirect » redirect loop / too many redirections

  • Resolved emgie


    I installed the plugin to allow my site to work in https mode after the activation of my HTTPS certificate.
    Since then, I have a lot of redirections problems when I update my site.
    Yesterday I made some changes to add testimonials and since my site is blocked, only the home page is visible.
    Someone recommend to desactivate the plug in and to contact you to see if you could help me. I will also contact lws in the meantime.
    It seems I have a redirect loop but I don’t understand how to fix it.
    Hope you can help me understand what’s wrong.
    thank you

    Here under, some messages received yesterday :

    Erreur de la base de données WordPress : [User ‘studi1367954’ has exceeded the ‘max_queries_per_hour’ resource (current value: 40000)]
    CREATE TABLE wp_users ( ID bigint(20) unsigned NOT NULL auto_increment, user_login varchar(60) NOT NULL default ”, user_pass varchar(255) NOT NULL default ”, user_nicename varchar(50) NOT NULL default ”, user_email varchar(100) NOT NULL default ”, user_url varchar(100) NOT NULL default ”, user_registered datetime NOT NULL default ‘0000-00-00 00:00:00’, user_activation_key varchar(255) NOT NULL default ”, user_status int(11) NOT NULL default ‘0’, display_name varchar(250) NOT NULL default ”, PRIMARY KEY (ID), KEY user_login_key (user_login), KEY user_nicename (user_nicename), KEY user_email (user_email) ) DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci

    OR this one (i have saved a word document with all the infos received, 74 pages in total… ) :

    L’API REST est l’une des façon pour WordPress ou d’autres applications de communiquer avec le serveur. Un exemple est l’écran de l’éditeur, qui s’appuie dessus pour afficher et enregistrer vos publications.

    L’appel à l’API REST a renvoyé le résultat inattendu suivant : (404) <!DOCTYPE HTML PUBLIC “-//W3C//DTD HTML 4.01//EN” “”> <html lang=”fr”> <head> <meta http-equiv=”Content-Type” content=”text/html; charset=utf-8″> <meta name=”robots” content=”none,noindex,nofollow”> <meta http-equiv=”cache-control” content=”no-cache”> <meta http-equiv=”pragma” content=”no-cache”> <TITLE>404 Not Found</TITLE> </HEAD> <BODY> <H1>Not Found</H1> The requested document was not found on this server. <P> <HR> <H1>Non Trouvé</H1> Le document demandé n’a pas été trouvé sur ce serveur. <P> <HR> <H1>No Encontrado</H1> El documento solicitado no se encontró en este servidor. <P> <HR> <ADDRESS> Web Server at | Powered by </ADDRESS> </BODY> </HTML> <!– – Unfortunately, Microsoft has added a clever new – “feature” to Internet Explorer. If the text of – an error’s message is “too small”, specifically – less than 512 bytes, Internet Explorer returns – its own error message. You can turn that off, – but it’s pretty tricky to find switch called – “smart error messages”. That means, of course, – that short error messages are censored by default. – IIS always returns error messages that are long – enough to make Internet Explorer happy. The – workaround is pretty simple: pad the error – message with a big comment like this to push it – over the five hundred and twelve bytes minimum. – Of course, that’s exactly what you’re reading – right now. –> .

    The page I need help with: [log in to see the link]

Viewing 3 replies - 1 through 3 (of 3 total)
  • @emgie this seems more an issue with IIS and certificate configuration. Please check with the hosting provider if there is no script/configuration at IIS trying to do the same thing.

    hey, what is ‘IIS’ ? 🙂

    @emgie IIS is the acronym for ‘Internet Information Services’. That’s what is showing up at the error message. This means that Your background server is Windows-based and not a Linux based one, which is recommended for WordPress solution. Anyway, It should work also there, but it seems the error, that is getting generated, comes from some configuration at the server configuration for the SSL and not from our plugin.

Viewing 3 replies - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.