unable to connect to wordpress site

  • Resolved mezam

    (@mezam)


    5 years, 8 months ago

    Hello, I’ve just installed WP 5.2.2 on RHEL 8 on AWS. Installation went smooth and I have the site running. However I cannot edit/add themes or plugins. When I go the theme section I get:
    An unexpected error occurred. Something may be wrong with www.ads-software.com or this server’s configuration

    I was able to manually upload the health check plugin and in the Site Health I get 3 errors:
    1. The REST API ecountered an error
    The REST API request failed due to an error.
    Error: [] cURL error 7:

    2. could not reach www.ads-software.com
    Your site is unable to reach www.ads-software.com at 198.143.164.251, and returned the error: cURL error 7:

    3. The loopback request to your site failed, this means features relying on them are not currently working as expected.
    Error encountered: (0) cURL error 7:

    What I did so far:
    1. amended all firewall rules on AWS side to allow ALL traffic temporarily.
    2. Disabled RHEL 8 firewall
    3. reinstalled WP
    4. delete the AWS server and started from scratch

    I’ve seen this error is very popular but no fix. Anything I can check on the WP installation? Installation is brand new, no content on the site yet

Viewing 9 replies - 1 through 9 (of 9 total)

  • Where is the wordpress instance installed and where are you trying to host the website ?

    Thread Starter mezam

    (@mezam)

    as specified in initial post, the WP instance is installed on a RHEL 8 server and it’s hosted on AWS

    Thread Starter mezam

    (@mezam)

    also.. my openssl is openssl-1:1.1.1-8.el8.x86_64

    Thread Starter mezam

    (@mezam)

    and if I try: curl -v https://api.www.ads-software.com
    I get:

    * Rebuilt URL to: https://api.www.ads-software.com/
    * Trying 198.143.164.251…
    * TCP_NODELAY set
    * Connected to api.www.ads-software.com (198.143.164.251) port 443 (#0)
    * ALPN, offering h2
    * ALPN, offering http/1.1
    * successfully set certificate verify locations:
    * CAfile: /etc/pki/tls/certs/ca-bundle.crt
    CApath: none
    * TLSv1.3 (OUT), TLS handshake, Client hello (1):
    * TLSv1.3 (IN), TLS handshake, Server hello (2):
    * TLSv1.3 (IN), TLS handshake, [no content] (0):
    * TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
    * TLSv1.3 (IN), TLS handshake, [no content] (0):
    * TLSv1.3 (IN), TLS handshake, Certificate (11):
    * TLSv1.3 (IN), TLS handshake, [no content] (0):
    * TLSv1.3 (IN), TLS handshake, CERT verify (15):
    * TLSv1.3 (IN), TLS handshake, [no content] (0):
    * TLSv1.3 (IN), TLS handshake, Finished (20):
    * TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1):
    * TLSv1.3 (OUT), TLS handshake, [no content] (0):
    * 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: OU=Domain Control Validated; CN=*.www.ads-software.com
    * start date: Nov 6 17:42:01 2017 GMT
    * expire date: Dec 15 20:11:21 2020 GMT
    * subjectAltName: host “api.www.ads-software.com” matched cert’s “*.www.ads-software.com”
    * issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=https://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority – G2
    * SSL certificate verify ok.

    Thread Starter mezam

    (@mezam)

    I solved it. The problem relied on SELinux. By default on RHEL is set to “enforcing”. I lowered it to “permissive” and it worked.

    Moderator Steven Stern (sterndata)

    (@sterndata)

    Volunteer Forum Moderator

    Use seaudit to figure out what rules you need to change. You should be able to get things working with SELinux enabled and enforcing.

    Thread Starter mezam

    (@mezam)

    many thanks Steve, I have only one web server and with no GUI.

    Moderator Steven Stern (sterndata)

    (@sterndata)

    Volunteer Forum Moderator

    https://linux.die.net/man/1/audit2allow

    Thread Starter mezam

    (@mezam)

    ??

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘unable to connect to wordpress site’ is closed to new replies.