allinvain

Members
 View Profile  See their activity

  • Posts

    13

  • Joined

  • Last visited

 Content Type 

Everything posted by allinvain

  1. allinvain
    When you get that red x error what I did was just refresh the page. It will spew a message saying that the operation is in progress and you need to wait. Wait a few minutes and hit refresh again (on your browser) and it should resume and proceed to the next step. I think updating via command line is far easier as long as you don't run into the issue that I did whereby the PHP version the docker container was running was incompatible with the command line update script (because of expected PHP version mismatch).
  2. allinvain
    Omg, this is frustrating, again updating the docker breaks NC. I'm on 25.0.7 after having upgraded manually via command line from 25.0.5. Is 26.0 compatible with PHP 8.2.6? And if so why did the docker maintainer update PHP. Is he expecting people to upgrade to the latest non-stable channel release? I guess on that note, what is the method to upgrade from 25.0.x to 26? --edit-- OK, so I figured it out. The trick is to roll back the container version to 25.0.2, and that should at least give you the ability to pull up the web interface again and run the upgrade script to 26.0 It worked for me. --further edit-- In case someone doesn't know how to roll back the container version just go to Docker and hit the edit button and in the "Repository" field edit the field to say "linuxserver/nextcloud:25.0.2" run through the web upgrade script in the nextcloud admin interface and after you've successfully updated to 26 to back to the docker setting, edit again and change the repository field and take out the ":25.0.2" Hope this helps.
  3. allinvain
    You could maybe try the command line update process. The issue is I'm not sure if that would work either if nextcloud php files expect to see PHP 7.3 or lower.
  4. allinvain
    Ok, so here is an update folks. After going through all the steps I outlined in my previous post I managed to get my Nextcloud container updated to version 24, and now the linuxserver nexcloud container works fine without any PHP errors 😁 Thanks Ccheese4 for pointing me in the right direction!
  5. allinvain
    I tried to follow your example above and try manually updating Nextcloud using it's own updater web interface: "Current version is 20.0.6. Update to Nextcloud 20.0.14 available. (channel: "stable")" As you can see I'm on an old version too but not as old as yours was. The issue I'm running into is the web updater times out constantly with errors such as these: "<html> <head><title>504 Gateway Time-out</title></head> <body> <center><h1>504 Gateway Time-out</h1></center> <hr><center>nginx/1.20.2</center> </body> </html> <!-- a padding to disable MSIE and Chrome friendly error page --> <!-- a padding to disable MSIE and Chrome friendly error page --> <!-- a padding to disable MSIE and Chrome friendly error page --> <!-- a padding to disable MSIE and Chrome friendly error page --> <!-- a padding to disable MSIE and Chrome friendly error page --> <!-- a padding to disable MSIE and Chrome friendly error page --> After numerous retries the update eventually went through and now I'm on 20.0.14 and was given the option to upgrade to 21.0.9 Not sure why these timeout errors happen but I will just stubbornly re-run the update and how it goes through as I slowly crawl my way up the version ladder. Let's hope it all goes well. If this ends up being the path forward then everyone running into the php error must follow the examples laid out here in this thread.
  6. allinvain
    Has anyone else been getting this error with the latest linuxserver nextcloud container "This version of Nextcloud is not compatible with > PHP 7.4. You are currently running 8.0.25." I just tried to remove linuxserver/nextcloud:24.0.5 repo tag out of curiosity and unfortunately it still crashes with the above error. For kicks I tried adding the nextcloud:25.0.1 tag, it downloaded new data but the same error popped up. --edit-- Wild theory but would this have something to do with the Unraid OS version?
  7. allinvain
    Go to the Unraid control panel and go to settings and then date & time.
  8. allinvain
    Can anyone confirm that the latest linuxserver container works? I used to use a reverse proxy but a year back I uninstalled that container and stopped using it. Could it be possible that nextcloud breaking is due to residual config issues? But as to how that would result in a incompatible PHP version error is beyond me.
  9. allinvain
    Yeah sounds like for sure the nextcloud container is busted. I'm guessing that even if you were to manually punch in the IP and port of your docker container (you can see the port mappings in the docker Unraid panel) it still fails. Well to put the docker in maintenance mode you'd have to use the command line - ie console. To pull up the console of a container you just click on the container's icon and click on Console which is right below WebUI. Putting it in maintenance mode is the easy part. The tricky part is backing up the database. If you forgot to note down your mariadb admin username and password and nextcloud database username and password then it will be a disaster. Backing up the nextcloud installation folder is a bit easier because you likely have a unraid file share that the nextcloud container already has a mapping to. You just copy the entire nextcloud directory and then move/copy the backup to the mounted nextcloud data directory share - it will be something like /mnt/user/Nextcloud To backup the database as per the instruction in the nextcloud manual it's the same scenario where you pull up a console prompt for the MariaDB container and copy/paste the command altering only the pertinent variable (ie database username/password etc). If you don't want to bother with all that you could always just recreate your entire nextcloud environment with a different container and manually copy the data files for each user you have. That data is not lost it's just sitting unaccessible via the nextcloud backup clients. Like I said your data should be in the unraid mounted nextcloud file share /mnt/user/Nextcloud (if you used the same scheme I used for example - you could've called the directory something else when you setup the container for the first time). Hope this helps a bit!
  10. allinvain
    So if you go to the docker section of the Unraid admin panel and click on the nextcloud container icon and then click on WebUI the nextcloud login page times out, correct? You can try and install the official nextcloud docker, but migrating data is not going to be fun. If you want to have an idea of the work involved, check this out: https://docs.nextcloud.com/server/latest/admin_manual/maintenance/backup.html https://docs.nextcloud.com/server/latest/admin_manual/maintenance/restore.html For me the nexcloud docker failed around the time I did an update (I have a habit of religiously updating my containers) so I assumed the two events are correlated in some fashion but it's possible it just broke on it's own. What triggered it I have no clue. I didn't have a lot of time to dig through the logs as I needed it working fast. I'm surprised that there is no "official" response yet from linuxserver crew.
  11. allinvain
    Hi Rick. I bet you anything you started having this issue after updating the docker container. This is precisely how it happened with me. I suggest rolling back the nextcloud docker version with the versioning tag trick someone outlined in an earlier post. Basically just edit the container and in the repository field change it to "linuxserver/nextcloud:24.0.5" Then hit install and it will roll back to that older repo. It seems to work for quite a few people.
  12. allinvain
    Hi everyone. Any update on a fix for the PHP version mismatch error. The trick to use the "linuxserver/nextcloud:24.0.5" version tag worked for me. It got me up and running but the version it installs is very out of date. Given my usage scenario (just local backup) it's not a big deal but some people out there may need the latest version. For the DB server I'm using the MariaDB container from Linuxserver.
  13. allinvain
    Hi guys. You all know what these are so I doubt I really need to tell you what they are. I have 3 of these. I recently moved over to LSI based SAS controllers and don't have a use for these anymore. Before you buy these be aware that these Marvell chipset based controllers have been reported to cause weird issues with unRAID. I ran these for 2+ years and never had any file system corruption or any problems, BUT I wasn't runnings VMs. I had vt-D enabled, but no VMs were running. If you plan to run VMs on your unRAID box maybe these are not for you, but if all you're looking for is an affordable JBOD card this model is a good choice. Asking price is $100 CAD per card (or whatever equivalent in USD). Cards are located in Canada - Southwestern Ontario, right across from Detroit, MI. Just the cards, no cables. I don't have original packaging anymore. Payment options: Cryptocurrencies: BTC, LTC, Monero, and more. Just ask me if I accept it. Most likely I will if it's one of the established altcoins and not some piece of trash scamcoin. CASH: In person if you live in southwestern Ontario. In this case I'd like to sell all 3 at once to spare me the driving around. PM me and ask. Interact EMT: this is a popular payment option in Canada. Direct person to person $ transfer from your bank account. PayPal: not ideal but yeah I'll take paypal if all other options are not possible. For BTC payments I can do escrow but we'd have to use an escrow provider from the bitcointalk forum. I have super good rep there (have the same username there as here) so if you want to trust me and skip the escrow nonsense I'm good with that too.