Support » Fixing WordPress » another "No site defined on this host."

  • Hi,

    I believe I have managed to install WordPress onto my VPS, I flagged the multisite as true. Updated my apache config, currently I have only one site pointing to the wordpress folder. I have configed the DB.

    I finaly managed to access the

    set up site name, user and password.

    Now I am unable to access the

    I keep receiving the “No site defined on this host.” error. I have been through a number of the debug pages, checked the DB which now has a number of wp_tables. But many of the help pages I visit seem to describe resolving these issue via a browser and I can not access any of these pages I keep getting the same “no site def..” error. I am now lost and confused.

    Where do I start to resolve, I need to do this via the console. I am happy editing or configuring the files directly, I just need to know which configs I need to check, what needs to be added, flagged ect.

    One thing I have not defined in wordpress are the two sites or host apache will be sending its way, neither have I defined a folders for these sites.

    Thank you for your time.



Viewing 2 replies - 1 through 2 (of 2 total)
  • httpd.conf =

    <VirtualHost *:80>
            DocumentRoot /..../apache/Umdana
    #       DocumentRoot /..../apache/wordpress
    <VirtualHost *:80>
            DocumentRoot /..../apache/BlogUmdana
    #       DocumentRoot /..../apache/wordpress

    Directory structure of apache folder

    apache]$ ls
    BlogUmdana  JoshuaSmith  Umdana  wordpress

    wordpress is installed into wordpress.

    wp-config.php =

    // ** MySQL settings - You can get this info from your web host ** //
    /** The name of the database for WordPress */
    define('DB_NAME', 'DB_NAME');
    /** MySQL database username */
    define('DB_USER', 'NAME_A');
    /** MySQL database password */
    define('DB_PASSWORD', '123456789');
    /** 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 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',         'put your unique phrase here');
    define('SECURE_AUTH_KEY',  'put your unique phrase here');
    define('LOGGED_IN_KEY',    'put your unique phrase here');
    define('NONCE_KEY',        'put your unique phrase here');
    define('AUTH_SALT',        'put your unique phrase here');
    define('SECURE_AUTH_SALT', 'put your unique phrase here');
    define('LOGGED_IN_SALT',   'put your unique phrase here');
    define('NONCE_SALT',       'put your unique phrase here');
     * 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_';
     * WordPress Localized Language, defaults to English.
     * Change this to localize WordPress. A corresponding MO file for the chosen
     * language must be installed to wp-content/languages. For example, install
     * to wp-content/languages and set WPLANG to 'de_DE' to enable German
     * language support.
    define('WPLANG', '');
     * 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);
    *Multi Site
    define('WP_ALLOW_MULTISITE', true);
    define('SUBDOMAIN_INSTALL', 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');

    gets me

    No site defined on this host. If you are the owner of this site, please check Debugging a WordPress Network for help.

    [No bumping, thank you.]

    Presumably this is a new installation of WordPress?

    In that case, you might consider wiping the DB and starting fresh, but setting it up as a normal single site install instead of a MultiSite install.

    Once you have the single site install working, then you can go back, add in the multisite flags, and convert it to a multisite system. Trying to set it up all at once with multisite is not recommended.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘another "No site defined on this host."’ is closed to new replies.