Unfortunately, before you posted this answer, I went into WordPress Dashboard –> General Settings and saw the fields “WordPress Address” and “Site Address” were filled with my IP address “http://104.236.88.248”. I replaced both fields with “cultureontrial.com” which apparently seems to have locked me out of my site.

Now the URL cultureontrial.com won’t work, I cannot access the login page from there, and the only login page that works, http://104.236.88.248/wp-login.php, redirects me to an error page every time i attempt to login. Also, when I enter http://104.236.88.248 my theme is deprecated, which it wasn’t before I made the change on the General Settings page.

Is there any way I can regain access to the backend of my site and change the General Settings page back to the way it was?? Please help! I will make a question about this later.

Hi there, according to someone else I messaged about this they can see my site just fine, and even access the wp-login page!! Here is my php file in full:

“<?php

define(‘DB_NAME’, 'wordpress’);

define('DB_USER’, 'username’);

define('DB_PASSWORD’, 'password’);

define('DB_HOST’, 'localhost’);

define('DB_CHARSET’, 'utf8’);

define('DB_COLLATE’, ”);

define('FS_METHOD’, 'direct’);

define('WP_HOME’,’http://cultureontrial.com’);

define('WP_SITEURL’,’http://cultureontrial.com’);

define('AUTHKEY’, 'HkGqbj]fzyMlqO||<P2e-[lXd0y}? +ZS}dR/VC#q-VV|eRr<HoOi{,SrK5A[GYn’);
define('SECUREAUTHKEY’, 'u,$6T]]XEKhhf]/eHt,<ZRrylcSR4;/mP^q2F,ejNy$JyPJ+gX0y6jbU8_HR’);
define('LOGGED_IN_KEY’, 'h8Q|k7YdT7Gn04.O7,OQF$Z:=3<P;+P&9:;JxwNL5H7yb]t-YQX<A0Q4EKNXb@!F’);
define('NONCE_KEY’, 'G]&J;6|9zx5>s!rgCab91c$+#Q58){mg|5fUxiYwG{GY}-K3k3a|:6?+BHeD =K5’);
define('AUTHSALT’, ’=VVWuT]4}&+t$Nr*aD>|Ls6<.#A1xa00$WrFtiRT20lY2=?zB)Bg)I;4/+cAgKF’);
define('SECUREAUTHSALT’, 'x-w}I/OrFw||Eg[ozZP)F5g:|@On+6?=Px,.<gj#xDw}<r0]#/ka@I]@h]nK’);
define('LOGGED_IN_SALT’, 'eNRrl=u/8=-|:w}tzetx[P.j|OSJs9J?K~?Yt};/N7vO:a;O@<&#b!7>|3Qq`zm’);
define('NONCESALT’, ’((O {.Vds8g$H,4$t+7mpg4)X5.KKNs-<ETwK<qZ3-o>+oFcH eIJ0}3:tj*-’);

$tableprefix = 'wp’;

define('WP_DEBUG’, false);

if ( !defined('ABSPATH’) )
define('ABSPATH’, dirname(FILE) . ’/’);

require_once(ABSPATH . 'wp-settings.php’);“

When I attempt to access cultureontrial.com from my computer it says "This site can’t be reached

cultureontrial.com’s server DNS address could not be found.”

I can access the site through 104.236.88.248, and I can access 104.236.88.248/wp-login, but when I attempt to login I get redirected to an error page. cultureontrial.com/wp-login doesn’t work for me either.

Can you let me know if you can see those webpages? According to someone else they are working on their computer.

thank you

thank you, I’m running apache2, I entered “ls /etc/apache2/sites-available” but that file directory only has the following three files listed:

000-default.conf
000-default-le-ssl.conf
default-ssl.conf

Hey there! This is what the 000-default.conf file looks like:

<VirtualHost *:80>
# The ServerName directive sets the request scheme, hostname and port th at
# the server uses to identify itself. This is used when creating
# redirection URLs. In the context of virtual hosts, the ServerName
# specifies what hostname must appear in the request’s Host: header to
# match this virtual host. For the default virtual host (this file) this
# value is not decisive as it is used as a last resort host regardless.
# However, you must set it for any further virtual host explicitly.
#ServerName www.example.com

    ServerAdmin webmaster@localhost
    DocumentRoot /var/www/html

    # Available loglevels: trace8, ..., trace1, debug, info, notice, warn,
    # error, crit, alert, emerg.
    # It is also possible to configure the loglevel for particular
    # modules, e.g.
    #LogLevel info ssl:warn

    ErrorLog ${APACHE_LOG_DIR}/error.log
    CustomLog ${APACHE_LOG_DIR}/access.log combined

    # For most configuration files from conf-available/, which are
    # enabled or disabled at a global level, it is possible to
    # include a line for only one particular virtual host. For example the
    # following line enables the CGI configuration for this host only
    # after it has been globally disabled with "a2disconf".
    #Include conf-available/serve-cgi-bin.conf

RewriteEngine on
RewriteCond %{SERVERNAME} =cultureontrial.com
RewriteRule ^ https://%{SERVERNAME}%{REQUEST_URI} [END,NE,R=permanent]
</VirtualHost>

vim: syntax=apache ts=4 sw=4 sts=4 sr noet

I have the nameservers for digital ocean in google domains (see here) and I also have the DNS records set up in digital ocean (here). They were set up this way before I set up wordpress and before wordpress, my URL site redirected to a blank apache page, so I assume they were set up correctly.

Sorry, I must have spoken too soon. I was able to edit the 000-default.conf file as you mentioned but my website still remains inaccessible as it was before. I noticed when I open 000-default-le-ssl.conf it also contains the line “#ServerName www.example.com”. Do I need to change that line as well?

best wishes