Jump to content

Dimtar

Members
  • Content Count

    511
  • Joined

  • Last visited

Community Reputation

6 Neutral

About Dimtar

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

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

  1. I used a password generator with 20 characters, I think you might be on to something with that. Thanks, will remember that.
  2. I re-did the mount but it didn't work. I deleted the user on the end SMB server and re-created them. It seems happy now, not sure what happened exactly as the user was enough to list the shares but I doubt this was the fault of the plugin. Its all working, thanks for a great plugin.
  3. The Unraid log Tools->System Log. Dec 2 02:47:03 Tower kernel: CIFS VFS: Send error in SessSetup = -13 Dec 2 02:47:03 Tower kernel: CIFS VFS: cifs_mount failed w/return code = -13 Dec 2 02:47:03 Tower unassigned.devices: Mount of '//192.168.25.78/RalphBackup' failed. Error message: mount error(13): Permission denied Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg) This confuses me but I will check the permissions again.
  4. I am running this plugin on the latest 6.8 RC7 I can connect to an SMB share but mounting doesn't work, not sure what I am doing wrong?
  5. My understanding is that it allows a higher lever of access then a regular container so you should only do it for containers you trust. Others on this board would likely have more information.
  6. I believe you need it for the container to work right but it seems I didn't make it the default in the template, i'll correct that now but you should turn it on and see what happens.
  7. @Vesko I am not sure what you're trying to do specifically but you should be able to just read the files off the array from the folder you told the container to use. I wouldn't recommend trying to move the NCP folder, you're likely to just break the container. If you want to store the files elsewhere select another folder on the array to use, instead of the appdata folder (in the container template). Thats just something I setup as the default. I've never used the other Nextcloud docker container for long so I can't comment on performance sorry. Technically given this is docker you can run both side by side but I think you would just be adding complexity for no benefit. I would pick one and stick with it. If you're happy with the LinuxServer Container I would just stick with that.
  8. @superslider it looks like not all the IPs match? You’re asking the container to run on 210 but telling NCP to allow it on 218, unless I am reading that wrong? Reading it back I see what you have done, you have followed the instructions but all the IPs need to match I think. I will update the wording in the template.
  9. That’s correct, most containers in unraid allow you set two locations but in this container you can’t. I appreciate this approach doesn’t work for everyone.
  10. Can you share a screenshot of your settings in the template?
  11. You can change the location in the template when you're setting it up, I defaulted it to /mnt/user/appdata/nextcloudpi but you can pick anyway as with most docker containers.
  12. I haven't had this issue personally, how long did you wait between hitting activate stopping it? What does the docker log say?
  13. This container is an all in one solution including LetsEncrypt support. If you need LE support for another container you will need to port forward to another port of your selection. So in your case if you might set port 553 on the host side for the container for SSL traffic. Then port forward that in your router. So it would end up being https://nextcloud.domain.com:553 If I am reading what you're asking right you wouldn't add anything to your existing LE config if you wanted to use this container.
  14. This is a support thread for the Nextcloudpi Docker Container for unRaid, from the home page: "NextCloudPi is a Nextcloud instance that is preinstalled and preconfigured, and includes a management interface with all the tools you need to self host your private data in a single package. This is an official open source community project that aims at making it easier for everyone to have control over their own data." For the purpose of unRaid this a single all in one container, an alternative to running nextcloud, database server and reverse proxy in separate containers. I am not the developer of this container but since I use it, I will do what I can to help people wanting to use it. Project homepage: https://ownyourbits.com/nextcloudpi/ Dockerhub homepage: https://hub.docker.com/r/ownyourbits/nextcloudpi You can find this container under the search team "Nextcloudpi" in the brilliant Community Applications system. For help with that please refer to the thread here: https://forums.unraid.net/topic/38582-plug-in-community-applications/ Setup: Once you selected the template in CA you will need to check 5 settings before you can start. Web port: By default this is set to port 80 but change based on your needs. Secure web por: By default this is set to port 443 but change based on your needs. Management port: By default this is set to port 4443 but it can be changed based on your needs. This is the management system behind Nextcloudpi, allowing you to make changes to most of the Nextcloud setup. Data folder: The default is /mnt/user/appdata/nextcloudpi so people can get up and running fast but this should be set somewhere on the array especially if you have alot of data. Making a share specifically for NCP is probably a good idea. Set IP: In the 'post argument' section please set the IP of your unRaid server, for example 192.168.0.5. When NCP starts up it will set this as a safe IP allowing you to continue setup once the container has started. PLEASE NOTE: The container can take upto 10 minutes to start when first installed, on startup it will crate the database and do most of the first setup. For this reason please be patient if the web interface doesn't respond shortly after start. Subsequent starts will be much faster. Once the container is running you can access it at https://unraidip:443, this page will list the generated admin user for Nextcloud and the management panel. These can be changed later but for now save them and hit activate. After getting the user details you can use the management system https://unraidip:4443 to setup your own domain, automatic updates and much more. If you have questions or issue please put them here. I or hopefully others will do what we can to help.