Forum Replies Created

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter mysmallspace19

    (@mysmallspace19)

    Ok thanks. Contacted Account team to try to get help with support access. Fingers crossed they contact me soon…

    Thread Starter mysmallspace19

    (@mysmallspace19)

    Thank you for that. I remembered we needed ro purge the cache once when we had a similar error. Thought I would check whilst waiting for contact. AWS seems to be a support glitch. I have upgraded but still don’t yet have access to support. No access to chat and no phone number. So I am completely stuck. I’ll just have to wait for my developer to pick up my messages. I am completely lost with this. 🙁

    Thread Starter mysmallspace19

    (@mysmallspace19)

    Thank you. My developer normally provides the support not AWS, so trying to upgrade the support package as my developer is on annual leave.

    In the meantime Cloudfare sent me this.

    “I checked further and it seems that the origin web server (note that server is nginx instead of cloudflare) responding with the same error message:

    $ curl -svk –resolve mysmallspace.co.uk:443:$origin https://mysmallspace.co.uk/ 2>&1 | egrep -i “(connected|^> |^< |body|error)”
    > GET / HTTP/1.1
    > Host: mysmallspace.co.uk
    > User-Agent: curl/7.63.0
    > Accept: */*
    >
    < HTTP/1.1 500 Internal Server Error
    < Server: nginx/1.6.2
    < Date: Tue, 22 Jan 2019 08:10:23 GMT
    < Content-Type: text/html; charset=utf-8
    < Transfer-Encoding: chunked
    < Connection: keep-alive
    < Expires: Wed, 11 Jan 1984 05:00:00 GMT
    < Cache-Control: no-cache, must-revalidate, max-age=0
    <
    <title>Database Error</title>
    <body>
    <h1>Error establishing a database connection</h1>
    </body>

    I cannot find my way around AWS at all to update wp-congig.php

    Can someone point me in the right direction?

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