Multisite Network Dashboard goes to http// (no colon)

  • Resolved dbellamytower

    (@dbellamytower)


    7 years, 8 months ago

    The Problem: My Multisite Network Dashboard redirects to “https://http//towersurfaces2017.heritagemarble.com/wp-admin/network/” even if I fix the “http//” to include the colon.

    The Back Story: My site was working fine until this morning when I was unceremoniously logged out, and I got a wrong pw error everytime I tried to log back in. I was updating a page, but I hadn’t changed anything special about the site. At first, I thought I was hacked, but after updating the database, I was getting a redirect back to the login page with no error when I tried to log in. I tried different browsers, and eventually cleared my cookies, which solved almost all of the log in issues, but now I have the aforementioned issue.

    The (Attempted) Solutions: I downloaded my database and did a search for “http//” with no luck, I called GoDaddy (they said it isn’t their issue,) I added define(‘WP_HOME’,’https://towersurfaces2017.heritagemarble.com’); define(‘WP_SITEURL’,’https://towersurfaces2017.heritagemarble.com’); to the wp-config file, I double checked the URLs in the database (as I can’t get to the settings in the network dashboard) a I have duplicated the error in two different browsers.

    I feel like I am in the twilight zone…

    htaccess:

    # BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
 
# uploaded files
RewriteRule ^([_0-9a-zA-Z-]+/)?files/(.+) wp-includes/ms-files.php?file=$2 [L]
 
# add a trailing slash to /wp-admin
RewriteRule ^([_0-9a-zA-Z-]+/)?wp-admin$ $1wp-admin/ [R=301,L]
 
RewriteCond %{REQUEST_FILENAME} -f [OR]
RewriteCond %{REQUEST_FILENAME} -d
RewriteRule ^ - [L]
RewriteRule  ^[_0-9a-zA-Z-]+/(wp-(content|admin|includes).*) $1 [L]
RewriteRule  ^[_0-9a-zA-Z-]+/(.*\.php)$ $1 [L]
RewriteRule . index.php [L]
</IfModule>
# END WordPress

    wp-config:

    define('WP_DEBUG', true);
/* Multisite */
define( 'WP_ALLOW_MULTISITE', true );
define('MULTISITE', true);
define('SUBDOMAIN_INSTALL', false);
define('DOMAIN_CURRENT_SITE', 'https://towersurfaces2017.heritagemarble.com');
define('WP_HOME','https://towersurfaces2017.heritagemarble.com');
define('WP_SITEURL','https://towersurfaces2017.heritagemarble.com');
define('PATH_CURRENT_SITE', '/');
define('SITE_ID_CURRENT_SITE', 1);
define('BLOG_ID_CURRENT_SITE', 1);
define('WP_MEMORY_LIMIT', '500M');
/* That's all, stop editing! Happy blogging. */
Viewing 2 replies - 1 through 2 (of 2 total)

  • This should clear things up. In fact, it’s likely that you won’t need the WP_HOME and WP_SITEURL at all. The issue was that DOMAIN_CURRENT_SITE should just be a FQDN without protocol, ie no https://. I recommend using schemeless protocols where ‘//’ will stand for both https:// and https:// for WP_HOME and WP_SITEURL.

    
define('WP_MEMORY_LIMIT', '500M');
define('WP_HOME','//towersurfaces2017.heritagemarble.com');
define('WP_SITEURL','//towersurfaces2017.heritagemarble.com');

define('WP_DEBUG', true);

/* Multisite */
define( 'WP_ALLOW_MULTISITE', true );
define('MULTISITE', true);
define('SUBDOMAIN_INSTALL', false);
define('DOMAIN_CURRENT_SITE', 'towersurfaces2017.heritagemarble.com');
define('PATH_CURRENT_SITE', '/');
define('SITE_ID_CURRENT_SITE', 1);
define('BLOG_ID_CURRENT_SITE', 1);

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

    (@dbellamytower)

    Has anyone ever told you, you are the man? Because you are the man.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Multisite Network Dashboard goes to http// (no colon)’ is closed to new replies.