• Bonjour tout le monde,

    Si je vous pose une question aujourd’hui c’est que je fais face à une situation assez complexe, je vous explique ??.

    Quand j’essaye de me connecter à l’admin WordPress d’un site, la page m’indique site inaccessible alors, que le site est toujours en ligne, je pense que c’est lié à un changement d’url dans les réglages que je ne peux plus modifier hélas.

    Je n’ai pas accès à l’hébergeur, car la personne à qui je refais le site est faché avec son dernier webmaster et du coup impossible de passer par le FTP.

    Merci pour votre aide très précieuse.

    • This topic was modified 2 years, 5 months ago by wouhapresque.
    • This topic was modified 2 years, 5 months ago by Jan Dembowski. Reason: Moved to Fixing WordPress, this is not an Everything else WordPress topic

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

Viewing 10 replies - 1 through 10 (of 10 total)
  • So you can’t reach the backend? What is the exact error message that is displayed?

    Possibly the WordPress URL is incorrect. If you can not reach the backend, then you can only change this setting via FTP or directly in the database. Here are the instructions: https://www.ads-software.com/support/article/changing-the-site-url/#changing-the-url-directly-in-the-database – there are no other ways. If the website owner wants to continue using the website, he has to “move”.

    Thread Starter wouhapresque

    (@wouhapresque)

    Le message est le suivant :

    Ce site est inaccessibleVérifiez si l’adresse site-inaccessible est correcte.
    S’il n’y a pas d’erreur, essayez de faire un diagnostic réseau Windows.
    DNS_PROBE_FINISHED_NXDOMAIN

    Moderator Steven Stern (sterndata)

    (@sterndata)

    Volunteer Forum Moderator

    What is your site’s URL? That error means there’s no DNS record for it.

    Thread Starter wouhapresque

    (@wouhapresque)

    L’url est [ redundant link removed ]

    Thread Starter wouhapresque

    (@wouhapresque)

    www odium-paradise com

    Moderator Steven Stern (sterndata)

    (@sterndata)

    Volunteer Forum Moderator

    The domain is registered, with name servers at 02switch.net, The domain points to 109.234.164.189. But that IP address doesn’t seem to go anywhere.

    When I try it, it gets redirected

    [sdstern@sds-desk ~]$ curl -v https://odium-paradise.com
    *   Trying 109.234.164.189:443...
    * Connected to odium-paradise.com (109.234.164.189) port 443 (#0)
    * ALPN, offering h2
    * ALPN, offering http/1.1
    *  CAfile: /etc/pki/tls/certs/ca-bundle.crt
    *  CApath: none
    * TLSv1.0 (OUT), TLS header, Certificate Status (22):
    * TLSv1.3 (OUT), TLS handshake, Client hello (1):
    * TLSv1.2 (IN), TLS header, Certificate Status (22):
    * TLSv1.3 (IN), TLS handshake, Server hello (2):
    * TLSv1.2 (IN), TLS header, Finished (20):
    * TLSv1.2 (IN), TLS header, Supplemental data (23):
    * TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
    * TLSv1.2 (IN), TLS header, Supplemental data (23):
    * TLSv1.3 (IN), TLS handshake, Certificate (11):
    * TLSv1.2 (IN), TLS header, Supplemental data (23):
    * TLSv1.3 (IN), TLS handshake, CERT verify (15):
    * TLSv1.2 (IN), TLS header, Supplemental data (23):
    * TLSv1.3 (IN), TLS handshake, Finished (20):
    * TLSv1.2 (OUT), TLS header, Finished (20):
    * TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
    * TLSv1.2 (OUT), TLS header, Supplemental data (23):
    * TLSv1.3 (OUT), TLS handshake, Finished (20):
    * SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
    * ALPN, server accepted to use h2
    * Server certificate:
    *  subject: CN=odium-paradise.com
    *  start date: Apr 22 17:48:11 2022 GMT
    *  expire date: Jul 21 17:48:10 2022 GMT
    *  subjectAltName: host "odium-paradise.com" matched cert's "odium-paradise.com"
    *  issuer: C=US; O=Let's Encrypt; CN=R3
    *  SSL certificate verify ok.
    * Using HTTP2, server supports multiplexing
    * Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
    * TLSv1.2 (OUT), TLS header, Supplemental data (23):
    * TLSv1.2 (OUT), TLS header, Supplemental data (23):
    * TLSv1.2 (OUT), TLS header, Supplemental data (23):
    * h2h3 [:method: GET]
    * h2h3 [:path: /]
    * h2h3 [:scheme: https]
    * h2h3 [:authority: odium-paradise.com]
    * h2h3 [user-agent: curl/7.82.0]
    * h2h3 [accept: */*]
    * Using Stream ID: 1 (easy handle 0x5643728ec0c0)
    * TLSv1.2 (OUT), TLS header, Supplemental data (23):
    > GET / HTTP/2
    > Host: odium-paradise.com
    > user-agent: curl/7.82.0
    > accept: */*
    > 
    * TLSv1.2 (IN), TLS header, Supplemental data (23):
    * TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
    * TLSv1.2 (IN), TLS header, Supplemental data (23):
    * TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
    * old SSL session ID is stale, removing
    * TLSv1.2 (IN), TLS header, Supplemental data (23):
    * Connection state changed (MAX_CONCURRENT_STREAMS == 128)!
    * TLSv1.2 (OUT), TLS header, Supplemental data (23):
    * TLSv1.2 (IN), TLS header, Supplemental data (23):
    < HTTP/2 301 
    < date: Mon, 06 Jun 2022 15:43:02 GMT
    < content-type: text/html; charset=UTF-8
    < content-length: 0
    < location: https://site-inaccessible/
    < x-redirect-by: WordPress
    < server: o2switch-PowerBoost-v3
    

    That x-redirect-by makes me think you have some plugin that’s doing the redirection. Try disabling all plugins.

    See https://www.wpbeginner.com/plugins/how-to-deactivate-all-plugins-when-not-able-to-access-wp-admin/

    Thread Starter wouhapresque

    (@wouhapresque)

    Merci, mais je n’ai malheureusement plus accès à wp-admin.

    Thread Starter wouhapresque

    (@wouhapresque)

    WordPress peut agir sur ce type de problème ?

    The problem is caused by a faulty configuration in your wordpress. The redirection that @sterndata describes is initiated by WordPress because the incorrect domain https://site-inaccessible is entered in the home URL. This makes your website inaccessible.

    Since you have no access to the wp-admin anymore, you have to change this setting manually in the database. How to do this is described here: https://www.ads-software.com/support/article/changing-the-site-url/#changing-the-url-directly-in-the-database – in home and siteurl must be the same URL for your website.

    The required access for the database can be provided by the support of your hoster. We here in the forum can not help you at this point.

    By the way, there is also a support area in your language: https://fr.www.ads-software.com/support/

    @sterndata: if you call wp-json via curl you can see the faulty setting ??

    Thread Starter wouhapresque

    (@wouhapresque)

    Merci pour votre aide

Viewing 10 replies - 1 through 10 (of 10 total)
  • The topic ‘Site inaccessible’ is closed to new replies.