• so as the title reads, I can’t browse the WordPress site using https://localhost on the Ubnutu server or anywhere on my local network LAN // but outside works fine, what should I look into ?

    thanks!

    • This topic was modified 2 weeks, 5 days ago by rompstar.
Viewing 13 replies - 1 through 13 (of 13 total)
  • Hello @rompstar,

    It seems like your query is missing some important details that could help us in troubleshooting the issue. Could you provide a bit more information about the following?

    1. Server Configuration: Are you using Apache, Nginx, or any other web server on your Ubuntu setup? Any specific configuration details for virtual hosts or binding?
    2. Local Network Configuration: Can you access other services or websites hosted on your Ubuntu server from within the LAN? Is this WordPress site the only service facing the issue?
    3. DNS Setup: Are you relying on any DNS configurations to access your site? For example, are you using a domain name mapped to your localhost or server IP?
    4. Firewall Settings: Have you checked the firewall rules on your Ubuntu server or network that might block requests from the local network? Are you using UFW or iptables?
    5. Hosts File: Have you checked whether the hosts file on your server or client machines is correctly set up to handle local network access?
    6. Is the issue only with localhost?: Can you try accessing the site using your server’s LAN IP, e.g., https://192.168.0.0, and see if it works that way?

    Thread Starter rompstar

    (@rompstar)

    I am using Apache on my own Ubnutu server… I can’t access on the localhost (the server) using http or https:// which is setup for localhost or 10.0.0.87.. but I just checked and I am able to access https or https://10.0.0.87 on my LAN computer (not the server) – just for whatever reason not on my server its self.. I have my real IP address setup not the one above and pointing DNS to it and I have port fordwarding setup for 80 and 443 at the ISP to the real IP / like I said the external works… when I am on my cell phone or at work…

    My firewall is disabled…

    my /etc/hosts is…

      GNU nano 7.2                          hosts                                  
    127.0.0.1 localhost
    127.0.1.1 raymond-PowerEdge-R310

    # The following lines are desirable for IPv6 capable hosts
    ::1     ip6-localhost ip6-loopback
    fe00::0 ip6-localnet
    ff00::0 ip6-mcastprefix
    ff02::1 ip6-allnodes
    ff02::2 ip6-allrouters

    hope this helps…

    • This reply was modified 2 weeks, 5 days ago by rompstar.
    • This reply was modified 2 weeks, 5 days ago by rompstar.
    • This reply was modified 2 weeks, 5 days ago by rompstar.
    • This reply was modified 2 weeks, 5 days ago by rompstar.
    • This reply was modified 2 weeks, 5 days ago by rompstar.
    Thread Starter rompstar

    (@rompstar)

    also here is my wp-config.php file / I recently restored from godaddy to my own server, so I am not quite sure what of these are old godaddy settings I don’t need anymore…

    <?php

    define( 'WP_CACHE', true ); // Boost Cache Plugin

    // BEGIN iThemes Security - Do not modify or remove this line

    // iThemes Security Config Details: 2

    define( 'DISALLOW_FILE_EDIT', true ); // Disable File Editor - Security > Settings > WordPress Tweaks > File Editor

    // END iThemes Security - Do not modify or remove this line

    /**

    ?* The base configuration for WordPress

    ?*

    ?* The wp-config.php creation script uses this file during the

    ?* installation. You don't have to use the web site, you can

    ?* copy this file to "wp-config.php" and fill in the values.

    ?*

    ?* This file contains the following configurations:

    ?*

    ?* * MySQL settings

    ?* * Secret keys

    ?* * Database table prefix

    ?* * ABSPATH

    ?*

    ?* @link https://codex.www.ads-software.com/Editing_wp-config.php

    ?*

    ?* @package WordPress

    ?*/

    define('WP_HOME','https://kodiakbrewing.com');

    define('WP_SITEURL','https://kodiakbrewing.com');

    // ** MySQL settings - You can get this info from your web host ** //

    /** The name of the database for WordPress */

    define('DB_NAME', 'wordpress');

    /** MySQL database username */

    define('DB_USER', 'wordpress');

    /** MySQL database password */

    define('DB_PASSWORD', 'secret');

    /** MySQL hostname */

    define( 'DB_HOST', 'localhost' );

    /** Database Charset to use in creating database tables. */

    define('DB_CHARSET', 'utf8');

    /** The Database Collate type. Don't change this if in doubt. */

    define('DB_COLLATE', '');

    /**#@+

    ?* Authentication Unique Keys and Salts.

    ?*

    ?* Change these to different unique phrases!

    ?* You can generate these using the {@link https://api.www.ads-software.com/secret-key/1.1/salt/ www.ads-software.com secret-key service}

    ?* You can change these at any point in time to invalidate all existing cookies. This will force all users to have to log in again.

    ?*

    ?* @since 2.6.0

    ?*/

    define('AUTH_KEY', ? ? ? ? 'v4+*ImLS)K(-93M#@MEg');

    define('SECURE_AUTH_KEY',? 'xqGRJ(x!RIX8JB/gdAhF');

    define('LOGGED_IN_KEY',? ? '2BBZTYFCFH82!#K4HXXU');

    define('NONCE_KEY',? ? ? ? '0F)Hz($Ij#JbQ$2SQHpa');

    define('AUTH_SALT',? ? ? ? '-P4SVZAac(0G1hA%*a c');

    define('SECURE_AUTH_SALT', 'mmG&GMUZ_+)cf7d$s//2');

    define('LOGGED_IN_SALT', ? 'nm%fQba&R2-q_rL-TTR@');

    define('NONCE_SALT', ? ? ? 'ndT_/vmF1nGR=3/4(5pk');

    /**#@-*/

    /**

    ?* WordPress Database Table prefix.

    ?*

    ?* You can have multiple installations in one database if you give each

    ?* a unique prefix. Only numbers, letters, and underscores please!

    ?*/

    $table_prefix? = 'wp_kn3f07md92_';

    define('ALTERNATE_WP_CRON', true);?

    /**

    ?* For developers: WordPress debugging mode.

    ?*

    ?* Change this to true to enable the display of notices during development.

    ?* It is strongly recommended that plugin and theme developers use WP_DEBUG

    ?* in their development environments.

    ?*

    ?* For information on other constants that can be used for debugging,

    ?* visit the Codex.

    ?*

    ?* @link https://codex.www.ads-software.com/Debugging_in_WordPress

    ?*/

    define('WP_DEBUG', false);

    define( 'WP_DEBUG_LOG', '/tmp/wp-errors.log' );

    //

    /* require_once( dirname( __FILE__ ) . '/gd-config.php' ); */

    define( 'FS_METHOD', 'direct');

    define('FS_CHMOD_DIR', (0705 & ~ umask()));

    define('FS_CHMOD_FILE', (0604 & ~ umask()));

    define( 'FORCE_SSL_ADMIN', true );

    /* That's all, stop editing! Happy blogging. */

    /** Absolute path to the WordPress directory. */

    if ( !defined('ABSPATH') )

    define('ABSPATH', dirname(__FILE__) . '/');

    /** Sets up WordPress vars and included files. */

    require_once(ABSPATH . 'wp-settings.php');
    • This reply was modified 2 weeks, 5 days ago by rompstar.
    • This reply was modified 2 weeks, 5 days ago by rompstar.
    Thread Starter rompstar

    (@rompstar)

    let me know if you want to see anything else… thanks!

    • This reply was modified 2 weeks, 5 days ago by rompstar.

    Hello @rompstar ,

    From what you’ve shared, here are a few things you could check to resolve this:

    I) Apache Configuration (Virtual Hosts):

    1. Ensure that your Apache configuration is properly set up to handle requests from both localhost and your LAN IP. Sometimes, virtual hosts may be set to listen only to certain IP addresses or domains. Check /etc/apache2/sites-available/000-default.conf or any custom virtual host configurations for proper ServerName or ServerAlias settings.
    2. Also, check that Apache is set to listen to both localhost and your LAN IP. You can verify this in /etc/apache2/ports.conf by ensuring it includes the following:

    Listen 80
    Listen 443

    II) Hosts File:

    • Your hosts file is likely fine, but just ensure there’s no typo or missing configuration. Since you’re trying to access it from your server itself, ensure 127.0.0.1 localhost is correctly set and that there are no conflicts.

    III) Firewall:

    Although you mentioned the firewall is disabled, double-check that no other networking rules are blocking local access (e.g., iptables or any external security service on the server that might restrict loopback requests).

    IV) DNS Resolution:

    1. Given that your site is accessible externally, it’s possible that requests to localhost or your LAN IP are being redirected or blocked internally. If you’re using a custom domain like kodiakbrewing.com, ensure that your DNS settings are correctly resolving to the internal server when accessed from within the LAN.
    2. Try accessing your server via https://127.0.0.1 instead of localhost directly on the server itself to see if it resolves.

    V) WP-Config Settings:

    • In your wp-config.php, you’ve defined WP_HOME and WP_SITEURL as https://kodiakbrewing.com. When you access the site locally via localhost or 10.0.0.87, WordPress may redirect to the domain you’ve set. You could try temporarily changing these values to https://localhost (or https://10.0.0.87) to test whether that resolves the issue:

    define('WP_HOME','https://localhost');
    define('WP_SITEURL','https://localhost');

    VI) SSL/HTTPS Configuration:

    • You have FORCE_SSL_ADMIN set to true, which forces HTTPS for admin access. If your SSL is misconfigured for localhost, it could be causing access issues. You can try setting this to false temporarily:
    define( 'FORCE_SSL_ADMIN', false );

    By testing with these changes and checking your Apache configuration, you should be able to figure out why localhost access is failing.

    Thread Starter rompstar

    (@rompstar)

    I will give this a shot later and report back, might not happen right away, as I am a bit busy with non-hobby work stuff ?? thanks!

    Thread Starter rompstar

    (@rompstar)

    here is my wordpress.conf file / does it look good to you ?

    <VirtualHost *:80>
    ServerName kodiakbrewing.com
    ServerAlias www.kodiakbrewing.com

    DocumentRoot /srv/www/wordpress
    <Directory /srv/www/wordpress>
    Options FollowSymLinks
    AllowOverride Limit Options FileInfo
    DirectoryIndex index.php
    Require all granted
    </Directory>
    <Directory /srv/www/wordpress/wp-content>
    Options FollowSymLinks
    Require all granted
    </Directory>
    RewriteEngine on
    RewriteCond %{SERVER_NAME} =www.kodiakbrewing.com [OR]
    RewriteCond %{SERVER_NAME} =kodiakbrewing.com
    RewriteRule ^ https://%{SERVER_NAME}%{REQUEST_URI} [END,NE,R=permanent]
    </VirtualHost>

    Hello @rompstar ,

    1. You’ve set AllowOverride Limit Options FileInfo, which is fine for enabling specific types of overrides, but if you want to ensure WordPress works optimally, you might want to set AllowOverride All. This allows .htaccess to manage all the necessary directives (like mod_rewrite for permalinks).
    2. The RewriteRule you’ve set for forcing HTTPS looks good, but make sure that your SSL certificate is correctly installed and active for both www.kodiakbrewing.com and kodiakbrewing.com.
    3. The Require all granted directive is set correctly, which means access shouldn’t be an issue. However, double-check that file permissions on /srv/www/wordpress and its subdirectories are correct (755 for directories and 644 for files).
    4. Since you’re able to access the site externally but not via localhost or on the server itself, there might be some issues with how localhost is being handled. Review your Apache error logs to see if there’s any additional information being logged when you try to access the site via localhost on your server.
    5. You’ve already shared your hosts file, and it looks fine. However, ensure the machine’s /etc/hosts file includes an entry like:

    127.0.0.1 kodiakbrewing.com
    127.0.0.1 www.kodiakbrewing.com

    If everything else looks fine, and you’re still facing issues, you could try to restart Apache after making the changes:

    sudo systemctl restart apache2

    Let me know if this helps or if there are still issues to look into!

    Thread Starter rompstar

    (@rompstar)

    ok / I did these two and now I can access on the local host / not sure of which of these two worked… but I can access the site now normally on the server it’s self local host…

    but if I try to access it on my other computer on my local LAN, it don’t work, if I type kodiakbrewing.com on my laptop which is connected to the same exact network at the server (internally), it don’t work… and if I do https://10.0.0.87 it sometimes works, but its very slow to load anything, takes forever and then I think, the REWRITE engine kicks in and tried to forward it all to kodiakbrewing.com, so nothing works / but at least on the local-server it works now, which is good, but not on my other laptop, not sure…

    also, I am pretty sure my SSL is setup correctly, I did the CertBot and it tested all fine and it works wonders and I even have a Cron line added to renew it every 90 days for free – I wasn’t going to pay godaddy some ridiculous $150 a year for a SSL key, because they don’t want to support open standard as it is not profitable for them.

    • This reply was modified 2 weeks, 4 days ago by rompstar.
    • This reply was modified 2 weeks, 4 days ago by rompstar.
    Thread Starter rompstar

    (@rompstar)

    btw, what does this do ? I have commented this out..

    define('ALTERNATE_WP_CRON', true); 

    Hello @rompstar ,

    Great to hear you can now access the site on localhost! As for accessing the site from other computers on your LAN, here are some points to consider:

    I) Internal DNS/Hosts Setup: It seems that the rewrite rule is kicking in when you’re trying to access it via https://10.0.0.87, and it’s trying to redirect to kodiakbrewing.com. Since you’re using an internal network, your other LAN devices might not be resolving kodiakbrewing.com properly.

    • Try adding an entry to the hosts file on your laptop (the one you’re using on the LAN) like
    10.0.0.87 kodiakbrewing.com
    10.0.0.87 www.kodiakbrewing.com

    This will tell your laptop to resolve kodiakbrewing.com to the local IP 10.0.0.87 instead of looking it up on an external DNS.

    II) Slow Loading on LAN: If the site is loading slowly when using the LAN IP, it could be related to a few things:

    • Check the network speed and see if there are any issues or bottlenecks between the devices.
    • If you’re trying to access the site via https://10.0.0.87, but your rewrite rules force everything to kodiakbrewing.com, this might cause a conflict if the browser is looking for valid SSL certificates for the internal IP. This could cause delays. You may want to test without the redirect by commenting out the rewrite rule and checking the loading speed.
    • Clear your browser cache or try another browser to make sure it’s not using cached DNS information or SSL settings.

    About ALTERNATE_WP_CRON

    You asked about the ALTERNATE_WP_CRON line:

    define('ALTERNATE_WP_CRON', true);

    This defines an alternate way for WordPress to run its scheduled tasks (CRON jobs). Normally, WordPress relies on visitors to trigger scheduled tasks (like publishing scheduled posts), but if you have issues with CRON not running on time due to low traffic or hosting limitations, this alternate method triggers CRON jobs on every page load.

    It’s a fallback mechanism for setups where the default method doesn’t work well. Since you’ve commented it out, WordPress is likely relying on its default CRON setup, which should work fine if you have regular traffic. If you’re not having scheduling issues (like missed scheduled posts or updates), you can leave it commented out.

    You can find about ALTERNATE_WP_CRON in the official WordPress documentation: Alternative Cron

    Thread Starter rompstar

    (@rompstar)

    thanks I will check those things out / are you using ChatGTP or some other model to generate answers ? its ok if you are, because I am learning that too, recently installed the 7B llama3.1 model, but soon will try the 40B as soon as I get more ram..

    ??

    Hello @rompstar,

    1. I follow official WordPress developer resources which include the code reference, https://developer.www.ads-software.com/
    2. I use Grammarly to avoid grammar mistakes and spelling.
    3. Also, I use Online Text Formater to write the text in an appealing format.

    Grammarly has some AI integration but the other two have not integrated with AI.

Viewing 13 replies - 1 through 13 (of 13 total)
  • You must be logged in to reply to this topic.