muddg

I am glad the information I posted was useful.

Next steps depend on your host and steps you’ve taken so far.

I used your “feedback” mechanism on your site. Check your email.

If you can get to the backend (using FTP) and modify your wp-config.php file (back it up first!) you might be able to get back in.

Read this article
https://www.beginwp.com/solve-ssl-error-login-issues-wordpress/

It has the code you can put into wp-config.php to change your site URL
but instead of changing it to https change it back to http.
You can either change it to https: or change it back to http: … adjust
the code in the article to fit your need but “please” make a copy of wp-config.php before you make any changes in case you cause a more serious error you can revert back to the original version.

This article also might be useful to “force” SSL login.
https://codex.www.ads-software.com/Administration_Over_SSL

I’ve experienced this problem before (usually on Apple computers).
It has always been a problem with the browser and usually some add-on.
So whatever browser is being used, try installing a different browser or disable all the browser plugins.

You could try the free version or the PRO version of duplicator.

https://www.ads-software.com/plugins/duplicator/

I’ve used several different (paid) packages including the one you mentioned and Duplicator is hands down the “most reliable” in my experience. I’ve used both free and paid versions dozens and dozens of times to backup, migrate to new domains, migrate to same domain but different host.

It takes less technical skill to use Duplicator that Updraft.

Here they list the hosting platforms on which it definitely works (has been tested)

https://snapcreek.com/duplicator/docs/faqs-tech?utm_source=duplicator_free&utm_medium=wp_org&utm_content=free_disclaimer&utm_campaign=duplicator_free#faq-hosts

….but I’ve used it on other platforms with no hitch including self-hosted Ubuntu, Linux and Windows servers (running Apache, Nginx, IIS, MySQL, MariaDB).

The only time I have encountered a problem is migrating from one host to another (it is usually a MySQL incompatibililty) but Duplicator support is very good…even for the free version.

The PRO version is not that expensive and well worth the “automated” backup features which you could (should) use once you get your site migrated.

Whatever you do, make sure you get the migration done before the old version is destroyed. Also check to see what version of WordPress, MySQL, PHP your old version is currently running on … useful for support to help you resolve problems. This plugin, for example, will display all that information for you.
https://www.ads-software.com/plugins/version-info/

If you try duplicator and have any questions, I will respond. (I have no affiliation with Duplicator…I am just a user).

If you search for 403.14 on IIS there are a ton of articles that suggest that the “Directory Browsing” feature is disabled. I didn’t find an article specific to Server 2016 but there are articles about IIS7 on 2012, 2015 and they all suggest this:

This problem occurs because the Web site does not have the Directory Browsing feature enabled, and the default document is not configured. To resolve this problem, use one of the following methods:

This is quite a good video that gets quickly to the point: shows you the setting in IIS to fix.https://www.youtube.com/watch?v=OmQlO0daduE

This article also has instructions but a bit more cryptic.
https://support.microsoft.com/en-us/kb/942062

If that is not your problem, the next thing I would look at are permissions.
Permissions on Windows are a notorious cause of installation and update problems in WordPress. Elevate permissions on the root directory of the WordPress install. A better method is to see if there is an error in the errors.log that will lead you to the specific directory or file that has the permission problem and change the permissions on that item only.

• This reply was modified 7 years, 11 months ago by muddg. Reason: spelling
• This reply was modified 7 years, 11 months ago by muddg. Reason: adding link

When you say you added those two lines of code to wp-config.php…it might be you haven’t put the code in the right place.

Sequence is important in some cases.

I’ve experienced that problem with (for example) the define(‘WP_POST_REVISIONS’, 15);
It has to appear before these two lines (can’t remember which) not after …
if ( !defined(‘ABSPATH’) )
define(‘ABSPATH’, dirname(__FILE__) . ‘/’);
require_once(ABSPATH . ‘wp-settings.php’);

It isn’t something that is always clearly documented in the codex.
Something to double check. I don’t see any specifics about it
in the documentation regarding auto updates.

The class logo_container is your key. Remove the float:left (i.e. float:none; in your child theme) then add margin-right:auto; margin-left:auto; to that class. That will center your logo but it throws your id selector header-right (Parks make life better) to the next line. You can fix that with position:relative; top:-90px; (or em or % could work better) but then it will definitely be messy on the mobile. So then you can use in your child theme @media only screen and (max-width: 981px) { insert css here } to adjust it for tablets and mobile.

Elegant Themes could do a much better job of making the Header and Logos more configurable in their customiser. If you look at it on a smart phone, the logo scales down to a very small size.

This is a good reference about scaling the logo in Divi
https://nerdnomads.com/divi-logo-size-customisation (I have no association with them).

It sounds like a permission problem to me…the fact that it can’t write the wp-config.php file…has nothing to do with the database. Yes a connection to the database is in the config file but….you would get a “can’t connect” to the database error if that was the problem.

Check the windows permissions on the root directory of the WP install…i.e. the directory where the wp-config.php file resides.

Whenever I installed or upgraded WordPress on IIS, I often had to elevate the permissions on the root folder to do the install or upgrade and then I would downgrade it again once the install or upgrade was done.

If you need more specifics, I can dig into my archives. I don’t run on IIS any more (thank heavens!)…as in your situation it was a client requirement.

What plugins do you have installed? It could be a plugin is causing the problem.

I resolved this problem by deleting the plugin and all the associated data, then downloading and installing the latest version and reconfiguring the forms from scratch.

A PITA.

Well I had already read that FAQ page. I also read every entry on the following page that could be “remotely” related to my problem.
https://www.fastsecurecontactform.com/faq-wordpress-version

I also forgot to mention I swapped to a different theme (Twenty Fifteen), to see if it was my theme. (Thesis). I get the same result.

So now what I’m going to do is delete the whole frigging plugin. Cleanup the options table and then I am going to try to install the plugin and setup my forms from scratch because something somewhere in the upgrading of the plugin has gone wrong.

I will report back.

Thanks for your prompt feedback. I am not sure what the message was…I’ll have to turn it back on momentarily to see. I was surprised that the plugin would cause this because it is so well used but I just could not see what the problem might be. I suspect blocked loopback now that you suggest it. I will have to check with the administrator. Once I confirm I will update this topic.

Thank you again for your prompt attention.

When I talk about the root folder, I am not talking about the wwwroot folder under the inetpub folder. I am referring to the physical folder where your wordpress files for the relevant website are installed.

In the IIS dashboard, when you “add a site” you have to specify the physical path where the website files will reside. The folder you specify here is what I refer to as the wordpress root folder. This is the folder you need to inspect with windows explorer (right click, properties, security tab) to see if the IUSR user has the correct permissions.

I can provide more specific details with screen shots if this still isn’t clear to you.

Describe what you mean exactly by full control.

Here’s what I do when I have permission problems on Windows, IIS7
(which is often):

Using Windows Explorer, right click on the root folder where WordPress is installed. Click on the security tab and you should see IUSR listed under the “Group or usesrname” panel.

Highlight the IUSR user to see which permissions exist. Under normal circumstances, you should see that Read & Execute, List folder contents, Read and Write are all ticked. This should be sufficient for normal WordPress operations and files and folders within this folder should inherit these permissions.

There are times when upgrading a plugin or WordPress itself, I find it necessary to add the “Modify” permission. I do my upgrade, then I go back and turn off the “Modify” permission. Not nice but sometimes the only way I can get upgrades done.

I hope this helps.

Ultimately the A Record should point to the IP address for the iPage host server…whatever that is.