PittPC

Members
  • Content Count

    15
  • Joined

  • Last visited

About PittPC

  • Rank
    Member

Recent Profile Visitors

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

  1. for Error A: the docker repo isnt fully specified your missing the ariadb at the end instead you have m lets do this stop all your dockers instances and remove them delete the docker directory and recreate it create these directories inside docker folder nextcloud_mariadb nextcloud (inside nextcloud create a dir called data) create nextcloud_data on the root on one of your volume not inside the docker folder create another folder called appdata inside that then rerun the docker run commands and we'll see if we get
  2. I tied it with that password that you tried and does work. I'm wondering if you have 2 docker directories somewhere in /volumes, check all directories and see if there are two. There was a bug where it wasnt wiping the harddrive if you did a new install. If you installed when that bug existed it may have mounted that volume with docker already there and created a duplicate. here is the code we use to install nextcloud if(isset($_POST['install_nextcloud'])){ // Check to see if docker is running $status_service_docker = exec("systemctl status docker | grep running");
  3. @Tido I'm wondering if special characters in the password are causing Nextcloud docker install to break on the shell level. Try using a a simple password of just password with all 3 check boxes checked then hit install. i'm curious if this is the problem.
  4. hahaha nice find! I was mad at something so I created a test file. I was trying things out initially in a virtual machine More updates coming. I will focus more on documentation today and maybe finish working on remote backup support
  5. Actually it pulls down the docker but the binary that there is compiled for intel arch x86. so it gets stuck in a loop at boot and never creates the files in the bitwarden dir. I think i may have a fix for this. Ill try to get it out this week. Good idea will do Fantastic Idea, i'll implement it in both areas the apps list and the logs and separate them nice! I never heard of this ill be sure to look into this one ! the install did not go as intended, it should have already configured the database using mysql, and everything configure
  6. Another update worth mentioning 1. Removed all the unnecessary plugin files reduced the amount of files in general, reworked some of the file hierarchy and layout
  7. Major Updates 1. The install.sh script now installs the debian backports version of smartmontools which doesn't depend on Python 2 and is a much newer version. This also sped up the install process a bit. 2. Added single disk support OS/Data 3. Updated the update system, dashboard now shows the latest version, when you choose updates it ill now show the changes between the installed version and the current. 4. We added Rescan disks button to add volume in setup as well as add volume in the main web ui app. 5. The system no longer reboots after setup it now direc
  8. @Tido BitwardenRS unfortunately is not compatible with arm32bit yet, hopefully soon Did your nextcloud install fully? Did it ask you to setup a database? sometimes it doesnt install fully when the system is under powered or under alot of load we are trying to fix it. All the apps use docker and the configuration is stored in /volumes/YOURFIRSTVOLUMENAME/docker/APPNAME
  9. We are working on a blog so followers can see updates, we will have this up and running by the end of the week. Thank you we will see if we can get a fix out this week Currently when you select check OS updates it only checks for OS updates and not simpnas updates, although when you select Upgrade Simpnas it will upgrade to the latest version and push you back to the dashboard. We will update this with a version number in dashboard and we will rename check for os updates to just check for updates. At the top it will display the most recent simpnas update along with a dro
  10. Third times a charm We made several updates today and tried to nail out some of the issues you were having plus additional small UI fixes and updates! 1. We don't use password confirmation anymore due to the eyeball, as we see it as redundant. 2. admin is close! and root works too. but it actually creates a user called administrator during setup, we now clarified it better in the final setup stage. 3. Yes the initial volume name cannot be changed this is due to the users home directories being placed there as well as the docker configs, although you
  11. Hi @guidol We figured it out, it had nothing to do with the networking but how it created volumes when using other devices other than HDDS like USB Sticks and mmc memory it would not detect them properly since we were using smartctl to scan for storage devices, now we have used a much better approach using lsblk to list all block devices. I noticed because of the screenshot at the top you sent me had garbled info under select disk. Please give SimpNAS one more shot of testing when you get time. Your testing is helping the project tremendously and we appreciate you!!
  12. Good idea! We submitted a new update you can now skip network configuration. also SSH will not be touched. Hopefully this fixes the issue your having. If you get time please give it another shot. Thanks!
  13. Your an excellent tester along with very clear given detail, I thank you for taking the time to test. We have only tested with the odroid hc2 and hc1 using armbian Buster flashed to an Micro SD card as well as an Dell Optiplex with Debian 10 installed on it. I'm going to order the M2 berry to do some further testing, also it looks interesting since it has a SATA port. This is the prcedure we have followed with installing SimpNAS on the oDroid HC1/HC2. We flashed a microSD with the latest Armbian buster. then I would ssh to it via the DHCP given address as root with the defa
  14. Hi @guidol thanks for trying our opensource project i'm sorry it didn't work out for you. To answer your first post, we moved the docker install to the final web-ui install phase. This was to prevent a DNS problem if Active Directory was configured during the server select phase. For your final post: When specifying an Address on the network setup page - it required to have the subnet CIDR on the end (example 192.168.1.200/24) if the /24 was not on the end it would cause the issues you are describing. Based on your feedback, you no longer have to put the CIDR at the end
  15. Hello I wanted to post on here regarding a new project we have been working on called SimpNAS. Its similar to OpenMediaVault or FreeNAS but simpler and more basic. Its currently in Beta but we are looking to have a stable release by the time Kobol ARM NAS gets released. It can be installed on armbian devices as long as it has two hard drives one for the OS and one for Data. For example we have it installed on an ODroid HC2, but can be installed on any PC. Feedback will be greatly appreciated. Check it out here https://simpnas.com Thanks for looking