• Resolved Carolyn Melo

    (@nubiesan)


    This is my staging site; it is not public. The production site has an SSL certificate but this one does not. The http was changed to https on the staging site and I can’t connect since the staging site has “unsupported protocol”.

    Any ideas on what I can do to get into the staging site and changing back to http? Thanks

    The page I need help with: [log in to see the link]

Viewing 9 replies - 1 through 9 (of 9 total)
  • Moderator Steven Stern (sterndata)

    (@sterndata)

    Volunteer Forum Moderator

    edit wp-config.php and set the site URL value to http://example.com

    https://wordpress.org/support/article/editing-wp-config-php/#wp_siteurl

    Thread Starter Carolyn Melo

    (@nubiesan)

    Thanks for the reply, but I have no idea what any of this means. Do I try to edit a file on the messed up site? Do I do this via ftp?

    Truly, I am clueless here

    Moderator Steven Stern (sterndata)

    (@sterndata)

    Volunteer Forum Moderator

    Download the file wp-config.php. Edit with your favorite editor. Upload the changed file.

    Thread Starter Carolyn Melo

    (@nubiesan)

    Where do I set the site url to http://example.com ?

    Sorry to be such a pest

    Moderator Steven Stern (sterndata)

    (@sterndata)

    Volunteer Forum Moderator

    Please follow the link I pasted above about editing wp-config.php.

    Thread Starter Carolyn Melo

    (@nubiesan)

    I read it several times and I don’t see where to change this. Here is the file:
    <?php
    //define(‘WP_CACHE’, true); // WP-Optimize Cache
    /**
    * 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.wordpress.org/Editing_wp-config.php
    *
    * @package WordPress
    */

    [redacted]

    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
    */

    [redacted]

    /**
    * 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_pr7fmxwtn7_’;
    /**
    * 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.wordpress.org/Debugging_in_WordPress
    */
    define( ‘WP_DEBUG’, false );
    //define( ‘WP_CACHE’, true );
    require_once( dirname( __FILE__ ) . ‘/gd-config.php’ );
    define( ‘FS_METHOD’, ‘direct’ );
    define( ‘FS_CHMOD_DIR’, (0705 & ~ umask()) );
    define( ‘FS_CHMOD_FILE’, (0604 & ~ umask()) );
    /* That’s all, stop editing! Happy publishing. */
    /** 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’ );

    Where do I change it and what do I change it to?

    Moderator Steven Stern (sterndata)

    (@sterndata)

    Volunteer Forum Moderator

    1. CHANGE YOUR DATABASE PASSWORD IMMEDIATELY as you just posted it publicly.

    2. Add a DEFINE after the wp-cache line: define( 'WP_SITEURL', 'http://example.com/wordpress' );

    3. What is the actual URL of your staging site? That’s what you put in there.

    Thread Starter Carolyn Melo

    (@nubiesan)

    I tried that but it didn’t work.

    IS there someone I could hire to fix this?

    Moderator Steven Stern (sterndata)

    (@sterndata)

    Volunteer Forum Moderator

    Not here.

    Please try http://jobs.wordpress.net/ or https://jetpack.pro/ and do not accept any hire offers posted to these forums.

    This topic will be closed as per the Forum Rules.

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

The topic ‘Unsupported Protocol’ is closed to new replies.