It is most likely a problem with permissions.
For security reasons, this is the required/recommended list of permissions for the files that most typically give problems to users:
directory ~/.ssh: 0700 (drwx------)
file ~/.ssh/authorized_keys: 0600 (-rw-------)
file ~/.ssh/config: 0600 (-rw-------)
file ~/.ssh/id_rsa (or other private keys): 0600 (-rw-------...
Looks like you have a couple of items to look at in the fullstack1.conf file:
Your DocumentRoot should point to the directory that visitors to the site will start from which, based on the <Directory> entity, should be:
The final slash in the <Directory> entity is unnecessary:
This is not just a permissions error, but a very specific permissions error.
The smb protocol does not support multiple credentials on the same connection from a client. You have another share from the same server on the local client that is using different credentials than the one you just tried to make.
Your options to resolve this are:
Determine what ...
NGINX does not have per-server user runtimes. If you need that then you need individual independent NGINX instances running with different configs and different sites.
It can be done with stock NGINX (building example setups right now) but you need different listen ports and config roots and cannot use the same config files for each instance. It is ...
Ubuntu Server or Ubuntu Desktop being used as a server? If it is Ubuntu Server:
A modern samba server also "announces" itself to the network using mDNS ( Avahi ) so that machines running MacOS and Linux can also "discover" it. The problem here is that Ubuntu Server does not install avahi by default so you will have to install it:
sudo apt ...
Hey so my problem was that I wanted to setup Plex on a remote dedicated Ubuntu server (the OS version is 18.04 LTS). And I got the same problem as the original poster. And I found a solution.
As noted by the original poster here in their comment reply, using localhost instead of the IP address worked for them. After finding my solution, it turns out that ...
As I have not found a solution to this question using systemd (Ubuntu 20.04, s3ql 3.8.0) easily I will post my solution here:
Description=mount s3ql filesystem
ExecStart=mount.s3ql --systemd --fg <other options> <storage url> <mount point>