Skip to main content
Log inGet free account

Troubleshooting

Get solutions to common filesystem troubleshooting scenarios.

Discuss in Slack
Edit this page on GitHub Report an issue with this doc

This section provides solutions to common filesystem troubleshooting scenarios.

Migrated WordPress sites errors

The Pantheon WordPress upstream uses the default Media Upload path (wp-content/uploads). You will get errors if you use any other path.

Simultaneous SFTP connections

Pantheon does not support simultaneous SFTP connections. Set your SFTP client to use no more than one simultaneous connection to avoid errors.

Unable to create directory path-to-folder. Is the parent directory writable by the server?

Sites migrated from other hosts may have custom or absolute paths in the Store Uploads in This Folder configuration. This can be resolved by using the recommended configuration:

  1. Go to the WordPress Admin Dashboard and go to Settings > Media (/wp-admin/options-media.php).

  2. Go to Uploading Files > Store uploads in this folder and update the field to contain only wp-content/uploads.

  3. Optional: Ensure that your wp-config.php file does not have a defined setting. For example,define(‘UPLOADS’, ‘wp-content/myimages’);.

Known Limitations of File Names and Permissions

File names and permissions are set by the system and cannot be changed.

Some modules or plugins might return the following error:

User notice: Key file "file:///files/private/public.key" permissions are not correct,
recommend changing to 600 or 660 instead of 770 in League\OAuth2\Server\CryptKey->__construct()
(line 59 of /code/vendor/league/oauth2-server/src/CryptKey.php)

Changing the file permissions to 770 from 660 via SFTP will cause a silent fail. The platform will not update the file permissions and will not return an error.

More Resources