Featured AI Products
Compute
Build, deploy, and scale cloud compute resources
Containers and Images
Safely store and manage containers and backups
Managed Databases
Fully managed resources running popular database engines
Management and Dev Tools
Control infrastructure and gather insights
Networking
Secure and control traffic to apps
Security
Help protect your account and resources with these security features
Storage
Store and access any amount of data reliably in the cloud
Browse all products
AI/ML
CMS
Data and IoT
Developer Tools
Gaming and Media
Hosting
Security and Networking
Startups and SMBs
Web and App Platforms
See all solutions
Community
Documentation
Developer Tools
Get Involved
Utilities and Help
Become a Partner
Marketplace
Pricing

- Community
- DigitalOcean
- Community
- DigitalOcean

ERROR: There was an error connecting to the server, Please verify the settings are correct.

Posted on May 24, 2017

Associated Droplet: negociofechado

Dear we are facing this page on our site, the same is without access, please kindly contact us regarding this message, because all the time is asking to verify the settings, follow the message below …

We wait and count with your support, we have the system without access …

THIS MESSAGE BELOW IS WHAT APPEARS WHEN YOU ACCESSED THE SITE:

ERROR: There was an error connecting to the server, Please verify the settings are correct.

Connection Information

To perform the requested action, WordPress needs to access your web server. Please enter your FTP credentials to proceed. If you do not remember your credentials, you should contact your web host.

Hostname 107.170.14.168 FTP Username negociosfechados FTP Password ••••• Connection Type FTP FTPS (SSL)

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Woet

May 24, 2017

Use SSH to fix your permissions using chmod and chown.

Jonathan Tittle

May 24, 2017

@carlosrpj

Unless you’ve installed and configured FTP software on your Droplet, you won’t be able to use FTP and would need to use SFTP.

That said, generally this isn’t required if proper permissions are setup to allow WordPress to read + write. How you’d go about this depends on whether you’re using Apache or NGINX.

On Apache, www-data is the default user that needs to own your files and directories, so if you are running Apache, you’d need to set ownership on the files.

For example, if you’re home directory (where index.php is) is:

/var/www/html

You may need to run:

chown -R www-data:www-data /var/www/html

NGINX works slightly different in that permissions need to be set for the user that is running the PHP process(es). By default, that’s www-data as well, so the same command could be used.

The developer cloud

Scale up as you grow — whether you're running one virtual machine or ten thousand.

View all products

Start building today

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Woet

May 24, 2017

Use SSH to fix your permissions using chmod and chown.

Jonathan Tittle

May 24, 2017

@carlosrpj

Unless you’ve installed and configured FTP software on your Droplet, you won’t be able to use FTP and would need to use SFTP.

That said, generally this isn’t required if proper permissions are setup to allow WordPress to read + write. How you’d go about this depends on whether you’re using Apache or NGINX.

On Apache, www-data is the default user that needs to own your files and directories, so if you are running Apache, you’d need to set ownership on the files.

For example, if you’re home directory (where index.php is) is:

/var/www/html

You may need to run:

chown -R www-data:www-data /var/www/html

NGINX works slightly different in that permissions need to be set for the user that is running the PHP process(es). By default, that’s www-data as well, so the same command could be used.

Report this

ERROR: There was an error connecting to the server, Please verify the settings are correct.

Become a contributor for community

DigitalOcean Documentation

Resources for startups and AI-native businesses

The developer cloud

Start building today