Forum Replies Created

Viewing 4 replies - 1 through 4 (of 4 total)
  • Thread Starter ralatalo

    (@ralatalo)

    Thank you, #1 filed as #65033
    #2 filed as #65034 and #3 #65036
    Thanks,

    Looks like I can’t remove my post, but I didn’t mean to hijack this thread, But on the positive note, if you’re self hosting you may have the same issue…. run:

    getenforce

    and if it report Enforcing, run:

    sudo setenforce 0 

    and see if that resolved the issue.

    At a high level, you will need to know who controls the DNS for your domain. Assuming you own the domain directly and have direct control over the DNS, you will likely have an A record for http://www.domain….
    which points towards your current hosting provider. You will need to create a second A record for www2.domain…. or some other name other than what you are currently pointing to your current provider. You will need to contract with some other hosting service for them to create a vhost for www2.domain… and then you build your site there. When you are ready to change, after you have tested everything, you ask your provider to update your vhost to use www instead of or in addition to www2 and change the DNS for http://www.domain…. to point to your new hosting service.

    The only rub is that if you got a free domain with service, you may not actually own the domain and may only be renting it.

    Well, I managed to fix my issue. Took me three days, completely dissecting the php code after enabling debugging options and still not fixing the issue. I finally pieced together some php database connection snippets to create a small testcase which still failed, then caught a break and googled the error message, wish I still had it…. anyway, my reason for posting is that I have two actually three suggestions:

    1) add a comment to wp-config-sample.php for:
    /** Database hostname */
    define( ‘DB_HOST’, ‘localhost’ );
    Something like:
    /** the format for DB_HOST can also contain either a port or socket or both **/
    /** the format for both is: ‘{hostname}:{port}:/path/to/socket’ **/

    2) After you enable debugging in wp-config.php and when you print the message:
    Include something similar to:
    The connection request below processed your configuration data as follows:
    mysqli_real_connect( {DBhandle} , host, dbuser, dbpassword, database, port, socket, client_flags );
    as host=’xxx’, dbuser=’xxxx’, dbpassword=’xxxxx’, database=’xxxxx’ , port=’xxxx’ , socket=’xxxxx’

    I did noticed that your passing in null for the database and I had originally thought that might be the issue as I had not granted usage to my mariadb user but my problem turned out to be opensuse appears to include SELinux by default as enforcing https://github.com/SELinuxProject/selinux/wiki/Fix-Policy-Problems once I ran setenforce 0, it was like a miracle as everything worked.. I still need to restore all my ‘damaged’ by extracting all the files to get a fresh install, but this brings me to my third suggestion.

    3) When you suggest people to check and verify their settings for including the username and password, you should also suggest that they verify that there is no firewall or SELinux security profile which could also block function.

    Thanks for letting me vent….



Viewing 4 replies - 1 through 4 (of 4 total)