Symbolic Link

[grandpa]

I have a situation that I do not completely understand, and so I'm not even sure how to frame a question or a search, so I'm hopeful that the good people at WebmasterWorld might point me in the right direction.

I have hosted a simple WP site on AWS Lightsail. Everything was great until a few days ago. Now I cannot update or install any plugins. The reason is because the directory cannot be created.

The default install is located at /opt/bitnami/wordpress
Somewhere along the line it appears that I, or a plugin, has created a symbolic link for the wp-content folder, which is now located at /bitnami/wordpress

I have tried disabling plugins to no avail.
I don't even know if I would recognize a reference to a symbolic link in any of the configuration files, or where such a reference might be.
All the file and folder permissions appear to be correct.
I have SSH and FTP access, so I can do whatever needs to be done, if I can just figure that out.

What should I be looking for?

[not2easy]

I would suggest that you take a look in your Settings to be sure that your WP install is where it should be. Generally, if you have a folder named wordpress it should be listed in your Settings page at the line for WordPress Address URL and the Site Address URL lines. Then check the Permalinks page to be sure you have the same structure listed for Permalink settings.

I can't tell where these folders are in relation to your domain's root folder, normally WordPress might be found at https://example.com/wordpress/ so that your wp-content folder with its plugins folder would be found at https://example.com/wordpress/wp-content/ --> https://example.com/wordpress/wp-content/plugins/ and these folders are created by WordPress during its installation.

[grandpa]

The problem was a symbolic link and the (new) wp-content folder was in a different location, and I was unable to change the install path, causing any plugin updates to fail, and preventing any new plugins from being installed. I still don't know why or how that symbolic link came to be, but I finally discovered the key to remove it. The rest of the evening was spent in rebuilding the wp-content.