Fresh Linux Mint 19.2 Install

Brand new fresh install onto Linux Mint 19.1, with a fresh LAMP. All went well. Then, when trying to browse from anywhere, it immediately redirects to ‘http://127.0.0.1/wordpress… then the error ‘This site can’t be reached…127.0.0.1 refused to connect’.

I’ve tried a gazillion of ‘solutions’ to this found online, including:
– Disable plugins
– Browser history (happens across the web..multiple machines)
– Removing .htaccess
– Modifications to wp-config.php

DEETS:—-
wp-config.php:
<?php^M
/**^M
* The base configuration for WordPress^M
*^M
* The wp-config.php creation script uses this file during the^M
* installation. You don’t have to use the web site, you can^M
* copy this file to ‘wp-config.php’ and fill in the values.^M
*^M
* This file contains the following configurations:^M
*^M
* * MySQL settings^M
* * Secret keys^M
* * Database table prefix^M
* * ABSPATH^M
*^M
* @link https://ww.wp.xz.cn/support/article/editing-wp-config-php/^M
*^M
* @package WordPress^M
*/^M
^M
// ** MySQL settings – You can get this info from your web host ** //^M
/** The name of the database for WordPress */^M
define( ‘DB_NAME’, ‘wordpress’ );^M
^M
/** MySQL database username */^M
define( ‘DB_USER’, ‘wpuser’ );^M
^M
/** MySQL database password */^M
define( ‘DB_PASSWORD’, ‘space’ );^M
^M
/** MySQL hostname */^M
define( ‘DB_HOST’, ‘localhost’ );^M
^M
/** Database Charset to use in creating database tables. */^M
define( ‘DB_CHARSET’, ‘utf8’ );^M
^M
/** The Database Collate type. Don’t change this if in doubt. */^M
‘wp-config.php’ [readonly] 90 lines, 2889 characters
——————————————
.htaccess:

# BEGIN WordPress
# The directives (lines) between ‘BEGIN WordPress’ and ‘END WordPress’ are
# dynamically generated, and should only be modified via WordPress filters.
# Any changes to the directives between these markers will be overwritten.

RewriteEngine On
RewriteRule .* – [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]
RewriteBase /wordpress/
RewriteRule ^index.php$ – [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /wordpress/index.php [L]

# END WordPress
—
apache2.conf:
# This is the main Apache server configuration file. It contains the
# configuration directives that give the server its instructions.
# See http://httpd.apache.org/docs/2.4/ for detailed information about
# the directives and /usr/share/doc/apache2/README.Debian about Debian specific
# hints.
#
#
# Summary of how the Apache 2 configuration works in Debian:
# The Apache 2 web server configuration in Debian is quite different to
# upstream’s suggested way to configure the web server. This is because Debian’s
# default Apache2 installation attempts to make adding and removing modules,
# virtual hosts, and extra configuration directives as flexible as possible, in
# order to make automating the changes and administering the server as easy as
# possible.

# It is split into several files forming the configuration hierarchy outlined
# below, all located in the /etc/apache2/ directory:
#
# /etc/apache2/
# |– apache2.conf
# | `– ports.conf
# |– mods-enabled
# | |– *.load
# | `– *.conf
# |– conf-enabled
# | `– *.conf
# `– sites-enabled
# `– *.conf
#
#
# * apache2.conf is the main configuration file (this file). It puts the pieces
# together by including all remaining configuration files when starting up the
# web server.
#
# * ports.conf is always included from the main configuration file. It is
# supposed to determine listening ports for incoming connections which can be
# customized anytime.
‘apache2.conf’ 227 lines, 7253 characters
# viewed by Web clients.
#

Require all denied

#
# The following directives define some format nicknames for use with
# a CustomLog directive.
#
# These deviate from the Common Log Format definitions in that they use %O
# (the actual bytes sent including headers) instead of %b (the size of the
# requested file), because the latter makes it impossible to detect partial
# requests.
#
# Note that the use of %{X-Forwarded-For}i instead of %h is not recommended.
# Use mod_remoteip instead.
#
LogFormat ‘%v:%p %h %l %u %t ‘%r’ %>s %O ‘%{Referer}i’ ‘%{User-Agent}i” vhost_combined
LogFormat ‘%h %l %u %t ‘%r’ %>s %O ‘%{Referer}i’ ‘%{User-Agent}i” combined
LogFormat ‘%h %l %u %t ‘%r’ %>s %O’ common
LogFormat ‘%{Referer}i -> %U’ referer
LogFormat ‘%{User-agent}i’ agent

# Include of directories ignores editors’ and dpkg’s backup files,
# see README.Debian for details.

# Include generic snippets of statements
IncludeOptional conf-enabled/*.conf

# Include the virtual host configurations:
IncludeOptional sites-enabled/*.conf
ServerName fredcolclough.com
# vim: syntax=apache ts=4 sw=4 sts=4 sr noet

Apr 28, 2021 12:10 am#3670858REPLY

oxynite
Member
Well…I sort of found the “answer/solution”:

found the reference in /sites-available/wp-config.php:

DocumentRoot = /var/www/html

I CHANGED IT to point to the wordpress folder below it:

DocumentRoot = /var/www/html/wordpress

BUT>….. now the site is all messed up!!!!!! IT’s full of broken stuff…. try it:
http://fredcolclough.com

I’m wondering if I need to actually move all the wordpress files into the /var/www/html root folder. ?? (Then maybe change DocumentRoot back??)

Thanks!
-Oxy.
——–
MORE:

Well…I sort of found the “answer/solution”:

found the reference in /sites-available/wp-config.php:

DocumentRoot = /var/www/html

I CHANGED IT to point to the wordpress folder below it:

DocumentRoot = /var/www/html/wordpress

BUT>….. now the site is all messed up!!!!!! IT’s full of broken stuff…. try it:
http://fredcolclough.com

I’m wondering if I need to actually move all the wordpress files into the /var/www/html root folder. ?? (Then maybe change DocumentRoot back??)

Thanks!
-Oxy.

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