Multisite Install – Main site site trying http
-
When I originally setup this multi-site install, it was done as http and not https. Since I have a few child sites now, I disabled the http and enabled the https binding with certificate in IIS.
The links for the child sites were all changed to https and work great. There permalink settings were also all changed to https from http. The main (root site; /) still tried to pull http and cannot since I have http disabled in IIS. Do not know how to fix that. The child sites were easy to fix via editing the site aND UNDER THE settings tabe, changing the Siteurl to https:// instead of http://. When I try this with the main site, Siteurl and Home are grayed out.I do not know if this is whay I cannot get the RSS Feed to work from child site to child site.
-
Hi Josh,
I don’t know if you done this yet, but I would log into phpmyadmin and change a couple values there as well…
Under the table wp_sitemeta you should be able to find the option for the main site from http://yoursite.com to https://yoursite.com.Hope that helps!
-KevinGo to phpmyadmin on IIS? is there not another way? My multisite install of WordPress is on a Server 2012 box running IIS. I have not used phpmyadmin on this paritcular box. I have ysed phpmyadmin when I had sites that were on a hosting servers server.
Did you read my reply post? I am running the wordpress multisite on a Server 2012 box running on IIS. So, I am not sure about your reference to running phpmyadmin.
I was able to get phpmyadmin working on my IIS SErver 2012 box. Now I am having trouble finding the table you are referencing.
Awesome! Sorry about not replying sooner.
You should be looking for the database that your WordPress install is on. Then within that database should be a table called wp_sitemeta
Within that table there will be a value that will allow you to change the http to https
Thank you for your reply.
There are many databases listed, how do I know which one belongs to the main site of my multi-site install?My list appears as the following:
New
information_schema
mysql
test
wordpress127
wordpress218
worpress297
wordpress334
wordpress348
wordpress356There are 24 “wordpress???” sites listed wordpress127 to wordpress980.
So, I am not sure which database I need toHello again josh,
To find the correct WordPress install you would need to find your wp-config.php on your main site and figure out which table it is writing to from there.
Once you have that you will be able to see if fixing the wp_sitemeta will help.
Below is my wp-config.php. I cannot find the table you are refering to.
** * The base configurations of the WordPress. * * This file has the following configurations: MySQL settings, Table Prefix, * Secret Keys, and ABSPATH. You can find more information by visiting * {@link https://codex.wordpress.org/Editing_wp-config.php Editing wp-config.php} * Codex page. You can get the MySQL settings from your web host. * * This file is used by the wp-config.php creation script during the * installation. You don't have to use the web site, you can just copy this file * to "wp-config.php" and fill in the values. * * @package WordPress */ // ** MySQL settings - You can get this info from your web host ** // /** The name of the database for WordPress */ define('DB_NAME', 'DELETED'); /** MySQL database username */ define('DB_USER', 'DELETED'); /** MySQL database password */ define('DB_PASSWORD', 'DELETED); /** 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.wordpress.org/secret-key/1.1/salt/ WordPress.org 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', 'Almostrightisalwayswrong!'); define('SECURE_AUTH_KEY', 'Almostrightisalwayswrong!'); define('LOGGED_IN_KEY', 'Almostrightisalwayswrong!'); define('NONCE_KEY', 'Almostrightisalwayswrong!'); define('AUTH_SALT', 'Almostrightisalwayswrong!'); define('SECURE_AUTH_SALT', 'Almostrightisalwayswrong!'); define('LOGGED_IN_SALT', 'Almostrightisalwayswrong!'); define('NONCE_SALT', 'Almostrightisalwayswrong!'); /**#@-*/ /** * 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_'; /** * 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. */ define('WP_DEBUG', false); define('WP_ALLOW_MULTISITE', true); define('MULTISITE', true); define('SUBDOMAIN_INSTALL', false); define('DOMAIN_CURRENT_SITE', 'wordpress.campbell.edu'); define('PATH_CURRENT_SITE', '/'); define('SITE_ID_CURRENT_SITE', 1); define('BLOG_ID_CURRENT_SITE', 1); define('WPPA_MULTISITE_INDIVIDUAL', true); define('ALLOW_UNFILTERED_UPLOADS', 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');I found the table the multisite used for the main install, “wordpress980”.
I have open that up and I cannot find a table named “wp_sitemeta”
I have the following tables:wp_11_commentmeta
wp_11_comments
wp_11_links
wp_11_options
wp_11_postmeta
wp_11_post
wp_11_terms
wp_11_term_relationships
wp_11_term taxonomy
wp_11_wppa_albums
wp_11_wppa_comments
wp_11_wppa_exif
wp_11_wppa_index
wp_11_wppa_iptc
wp_11_wppa_photos
wp_11_wppa_rating
wp_11_wppa_sessionThe above table structure repeates for wp_12 & wp_13.
So, I cannot find the table you are referring to.I finally found the table named “wp_sitemeta” and changed the value of “siturl” from http://wordpres.campbell.edu to https://wordpress.campbell.edu. When I go the the dashboard and go to Sites, them try to visit the site I get a 404 not found. When I go to the dashboard of the main site and look at the settings, it still shows the main site url as http://wordpress.campbell.edu. MY change was save and I did a iisreset and restart IIS after the change, but it does not reflect the change. I do not know what the problem is. When I go back into phpmyadmin and check the siteurl value, it is showing my change from hhtp to https. The domain is showing as wordpress.campbeel.edu in table “wp-site”. So, I do not know what I am missing.
This works for me – https://wordpress.campbell.edu/
This does NOT work for me (404) – http://wordpress.campbell.edu/
This tells me that your IIS configuration is not set correctly for http. The other question is do you want want users to access your site via http? If not you will need to configure IIS to redirect all http traffic to https.
If you can edit your post above and REMOVE your passwords and other sensitive info.
That is not the problem. I do not allow http. Read the above thread to this post. The problem is when the original multi-site was installed it as http. I changed it to https (or at l;east all the child sites are https). The problem is in the main site is still thinking it is suppose to be http, even though I change the siteurl in the database table “wp_sitemeta” from http to https. The changed is not reflect in the settings of the main (root / site).
DO NOT EVER EVER EVET POST YOUR ENTIRE WP-CONFIG FILE IN A PUBLIC FORUM! YOU NEED TO CHANGE YOUR DB PASSWORD RIGHT NOW
I’ve edited your post, but you just posted your USER ID AND PASSWORD in a PUBLIC FORUM. ANYONE who read this post within the last 20 hours knows it.
PLEASE CHANGE IT RIGHT NOW.
Yes, I’m shouting at you.
If anyone asks you to post from your wp-config in Multisite, they ONLY mean this:
define('WP_ALLOW_MULTISITE', true); define('MULTISITE', true); define('SUBDOMAIN_INSTALL', false); define('DOMAIN_CURRENT_SITE', 'wordpress.campbell.edu'); define('PATH_CURRENT_SITE', '/'); define('SITE_ID_CURRENT_SITE', 1); define('BLOG_ID_CURRENT_SITE', 1); define('WPPA_MULTISITE_INDIVIDUAL', true); define('ALLOW_UNFILTERED_UPLOADS', true);*AHEM* Now.
The easiest thing to do is grep your DB for
http://wordpress.campbell.eduand replace withhttps://wordpress.campbell.edubecuase the simple answer is this: You missed something.And Multisite makes it more complex since you have to check the
wp_optionstables for all sites. You’ll look insiteurlon each options table, and alsohome.If you have wp-cli use that, otherwise I recommend https://github.com/interconnectit/Search-Replace-DB
Moderator please delete the post with my wp-config. I did not mean to post the entire thing.
Ipstenu (Mika Epstein),
Thank you for editing my post and catching that. I do not know what I was thinking when I posted that. I forgot that that info would be in there. Would you please edit you post to remove the point out and yelling so that it does not draw further attention.
What is the easiest way yo change this password without affecting the sites currently up? Do I just change it in myphpadmin?
The topic ‘Multisite Install – Main site site trying http’ is closed to new replies.