Not Found The requested document was not found on this server. http://dominio/wp-login.php

[mauricio]

I installed plesk in google cloud in vm centeos7.
But wordpres fails to work.
Plesk installs the application creates the database and all that is required to operate. when the time to configure the application to precionar the link should take me to wp-login.php file does not work arrives. message appears

http: //dominiol/wp-login.php
Not Found - The requested document was not found on this server.

I changed the permissions to the httpdocs folder, modified httpd.conf, change permissions wp-config.php file, also did with wp-login.php.
But nothing seems to work. anyone have any idea what could be ...?

 

[IgorG]

If you did default wordpress installation in Plesk - correct URL for this wordpress is http://domain.com/wordpress/ but not http: //domain.com/wp-login.php

 

[mauricio]

servidor : centeos 7

 

[RuslanT]

Hello,
In your case domain's hosting IP should be internal but all DNS records should points to the external IP. Most probably when you change hosting IP to the internal IP you site resolves few hours to the external IP due SOA TTL but after that it stops resolving and became inaccessible.
It looks like google cloud infrastructure is very similar to amazon EC2. You can try to use ami_linux_utils from http://kb.odin.com/122222 but you have to pass the External IP to them manually:

# /usr/local/psa/bin/amazon_setup_ip <EXT IP>
# /usr/local/psa/bin/amazon_install_dns_template <EXT IP>

Also you'll need to sync all your DNS zone with the modified DNS template:

1. If the IP was changed on a Plesk implementation that already hosts domains:
   
   • Log in to Plesk and go to Tools & Setting > General Settings > DNS Template settings
   • Check that all "A" records from the server-wide DNS template point to the new external IP, and synchronize the changes to all zones by pressing Apply DNS Template Changes and selecting All zones.
   Keep in mind that all unchanged PTR and A-type DNS records that point to the old public IP in all DNS zones will be changed to the new public IP.
   
   You can find additional details on the DNS Template synchronization procedure in the Administrator's Guide: Performing Mass Operations over DNS Zones.
   

 

[mauricio]

thanks for your help now works without problem