Jump to content

Djoss

Community Developer
  • Content Count

    1276
  • Joined

  • Last visited

  • Days Won

    9

Djoss last won the day on April 12

Djoss had the most liked content!

Community Reputation

248 Very Good

3 Followers

About Djoss

  • Rank
    Advanced Member

Converted

  • Gender
    Male
  • Location
    Canada

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Ah I didn't realized that you had this type of setup. The easiest way is to use a DNS name for each service. But, if you want to put Plex under a subfolder, try (with the initial config you shared) ) to set the forward ip to "10.0.1.100/" (ending slash is important).
  2. Here what should be the permissions/ownership of /mnt/user/appdata/FileZilla: drwxrwxrwx 1 nobody users 12 Jan 11 12:30 FileZilla/
  3. You don't need to use a custom location. Just set the forwarding IP to 10.0.1.100, the port to 32400 and make sure web socket support is enabled.
  4. You seem to have an issue with DNS resolution. Maybe your router? Can you run nslookup on other machine than unRAID ?
  5. When you say that inodes are different, is it from unRAID or from the container?
  6. Looks like you have wrong permissions on the appdata folder?
  7. Yes this will for sure be done
  8. Can your domain names be resolved using this service?: https://mxtoolbox.com/DNSLookup.aspx
  9. So nextcloud is not able to resolve the DNS name? Did you try to seek support from the nextcloud's thread?
  10. I never tried to backup to a device on my local network, but I guess that the speed can be impacted by multiple features: compression, encryption, etc.
  11. The "Scheme" setting configures the way your internal service is accessed. It doesn't impact how it is accessed externally (from the internet).
  12. Can you confirm that you are still getting the error and if yes take the content of /mnt/user/a ppdata/NginxProxyManager/nginx/resolvers.conf at that moment?
  13. Nothing has to be done, it should work by default. Do you have issue with all file types?
  14. No sure why you are getting permission errors. Everything looks good. Other than changing mappings to /output and /storage, did you made other changes to the template? As a last resort, your could try to re-create your docker.img to see if it helps.
  15. Normally this is fixed by clearing your browser's cache.