installing WP on google-vm

  • edwardsmark

    (@edwardsmark)


    1 month, 1 week ago

    hello – i have installed WP over the years more times than i can count but never tried on google-vm before today.

    on a new WP installation on a new google-vm, i get the following error on the plug-in page:

    An unexpected error occurred. Something may be wrong with WordPress.org or this server’s configuration. If you continue to have problems, please try the support forums.

    i can successfully do a dig wordpress.org; and ping wordpress.org; on the server, and both of these commands resolve to 198.143.164.252

    do i absolutely first need to get https:// working or something like that? or is there some other port i need to first open? i have not installed FTP or anything like that yet.

    suggestions? (i am just about ready to do all this again on NameCheap or similar & give up on google-vm)

    EDIT: i added define('WP_HTTP_BLOCK_EXTERNAL', false); to wp-config.php but this did not fix it.

    • This topic was modified 1 month, 1 week ago by edwardsmark.
    • This topic was modified 1 month, 1 week ago by edwardsmark.
Viewing 4 replies - 1 through 4 (of 4 total)
  • Thread Starter edwardsmark

    (@edwardsmark)

    1 month, 1 week ago

    note: i have two google-vm servers, and one lets me add WP plug-ins, the other does not. both are LAMP. i checked ownership (apache:apache) and permissions, both are identical.

    so at this point, i have ran out of things to try.

    Thread Starter edwardsmark

    (@edwardsmark)

    1 month ago

    time to cut losses, moving over to NameCheap

    Joakim

    (@joa-kim)

    1 month ago

    Hi, I suggest you enable WordPress debugging to see if any errors are being logged to the wp-content/debug.log file. You can do this by adding the following lines to your wp-config.php file:

    define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );

    Also, check your server’s Google VM error logs for any clues. Look for any PHP errors or other relevant messages that might indicate what’s causing the issue.

    Thread Starter edwardsmark

    (@edwardsmark)

    1 month ago

    hi Joakim –

    i probably should have done that, but its been my experience that sometimes just getting the log files to be created in the first place (and even finding where they are) takes a bit of work.

    also i forgot all about wp-content/debug.log — gotta remember to look there first. thank you for reminding me that it even exists.

    but since google-vm was being so weird in the first place i cut my losses & got everything installed on NameCheap in a fraction of the time, and oddly enough, a fraction of the cost.

    Google-vm is cool stuff for sure, but i even ran into an issue where google-vm didnt seem to “like” a domain with a (dot)dev extension. so i switched over to (dot)org and fixed it. crap like that is a headache i dont need. 😋

Viewing 4 replies - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.