j0nnymoe

Members
  • Posts

    346
  • Joined

  • Last visited

Posts posted by j0nnymoe

  1. Rolling back to an older image doesn't mean it's a "fix". You shouldn't have your database containers on auto update. Having a database update while it's beening accessed by X application (in this case nextcloud) is just asking for trouble and likely going to cause corruption or data loss.

  2. On 8/23/2021 at 5:55 PM, Tucubanito07 said:

    When ever the tag gets update to ALPINE = LATEST, what will happen to the application if we update it then? Will it corrupt the database or would we have to do something before we update to make sure it does not corrupt the databases or mess up anything when updating? Also, why are you guys going to Alpine? What's the benefits?

    Less so benefits for unraid users (x86_64) but better for our armhf / aarch64 users as mariadb don't release up to date versions for those platforms on ubuntu base.

    • Like 1
  3. 17 hours ago, ich777 said:

    How do I migrate to the alpine image:

    ******************************************************
    ******************************************************
    * *
    * *
    * This image will soon be rebased *
    * from ubuntu to alpine. *
    * Please be aware, this may cause issues *
    * It is strongly recommended to make backups *
    * of your config and databases before *
    * updating your image to the alpine base. *
    * *
    * *
    ******************************************************
    ******************************************************

     

    Upgrading to `:latest` will put you on alpine.

  4. 14 hours ago, jafi said:

    After update I got this:

     

    
    Internal Server Error
    
    The server encountered an internal error and was unable to complete your request.
    Please contact the server administrator if this error reappears multiple times, please include the technical details below in your report.
    More details can be found in the server log.

     

    I have no idea how to hunt the problem.

    Probably best start by providing info on the container - Have you been keeping nextcloud updated within the container? Nginx logs? nextcloud logs?

    • Like 1
  5. 19 hours ago, darkrom said:

    So what is next for people who need openvpn?  I run Wireguard yes, but many places block UDP so I need openvpn as a fallback.    Is it even safe/secure to use if there will be no further updates?

     

    Does openVPN-AS still get updates, just not this particular container?

    OpenVPN-AS still gets updated from openvpn itself. The reason we've dropped it is due to the constant band-aid fixes we have to do and something breaks on every update they push out.

  6. On 6/28/2021 at 4:41 PM, nadbmal said:

    Very annoying that OpenVPN-as is one of the most important/critical dockers I run and its the one that always randomly breaks and I don't notice it until it's too late when I'm not home and need to remote in. 

    Changing the repo to linuxserver/openvpn-as:2.8.8-cbf850a0-Ubuntu18-ls122 according to the comment above fixed it anyway. Hopefully it'll stay fixed since that version number/repo adress shouldn't change.

    We've depreciated the container now so there will be no further updates/changes/support for the container.

  7. 1 hour ago, andreidelait said:

    So I updated to 21.0.1 today and I had a few errors after. I will address them here and I hope they will help others to fix them quick.

     

    I had errors referring to my nginx config /.well-known/carddav, caldav, webfinger etc. Here is my swag nginx config section about that

     

    
    location ^~ /.well-known {
          location = /.well-known/carddav     { return 301 /remote.php/dav/; }
          location = /.well-known/caldav      { return 301 /remote.php/dav/; }
          location = /.well-known/webfinger   { return 301 /index.php$uri; }
          location ^~ /.well-known            { return 301 /index.php$uri; }
    
          try_files $uri $uri/ =404;
          }

     

    I had them different before and apparently they do not work in this version.

    Also I had an error reffering to some db indices. Fo these you go into nextcloud container console and run

    
    sudo -u abc php /config/www/nextcloud/occ db:add-missing-indices

     

    And another one was reffering to default phone region. You have to add your phone region in config.php

    
    'default_phone_region' => 'GB',

    You have to replace GB with your country specific code. You can find it here

     

    I hope this is useful info.

    The well-known info needs to be added to the nextcloud nginx config and not the swag config. We've already updated this and mentioned it in the changelog for nextcloud.

    • Like 1
  8. 4 hours ago, skois said:

    Could you please be more specific? What exactly to add?
    Also I guess you mean to put "that" in the "/appdata/nextcloud/ngiong/site-confs/default"

    Yea apologies - we just need to add the additional nginx bits to the site config file. Though if you've done it manually, all good 👍

  9. 4 hours ago, DayspringGaming said:

    So I've spent the better part of 3 hours on this tonight and I have 2 "errors" left in my Nextcloud setup. 

    Fresh 21.0.0 install
    Fresh SWAG install

    Using duckdns.org and Spaceinvader's setup video. 

     



    I can't for the life of me figure out what to edit and where. I see NGINX posts saying to edit something here, I see others saying to edit .htaccess files. None of the searches I've done here and abroad have lead to a concrete "edit this, do this here" answer.

    At the end of my proverbial rope and patience. 

    Add this to the site config within the nextcloud container. We plan to add this soon.

  10. 37 minutes ago, TexasUnraid said:

    I need a headless kodi install with VNC that I can view from multiple computers.

     

    I tried installing this container as it looked like a perfect fit but can't figure it out.

     

    When I open the VNC I am presented with a really strange GUI that is nothing like kodi on any of my other devices.

    firefox_D8Y0Kt6VUJ.thumb.jpg.c9a1584efd493eadeedadeddebe65568.jpg

     

    Vs all my other devices:

     

    kodi-18-2-e1550206283796.thumb.jpg.e1c4b3d60755eeef4c79d46ea2e99b2e.jpg

     

     

    The settings menu in particular is completely different. I can not find any place to scan a folder for media? It is also missing most of the settings options. How do I add media to this kodi?

     

    275350511_Screenshot_2021-01-29Kodi.thumb.png.6776f488c5b654cdd34a4db87883178d.png

     

    Is it possible to go to the stock kodi skin?

    It's a headless install as in zero display. It's not possible to use vnc with this. What you're seeing is actually the native Kodi webui.

  11. 8 hours ago, toolmanz said:

    Well a little more information on the problem .....

     

    The docker is running and except for the webui seems to be functioning as expected.

     

    I did all of the maintenance as I would normally do with files and indices through OCC ..... not a problem.

     

    I checked the PHP version and it is up to date (Jan 7-2021) [php -v in terminal]

     

    "PHP 7.4.14 (cli) (built: Jan  7 2021 11:46:25) ( NTS )
    Copyright (c) The PHP Group
    Zend Engine v3.4.0, Copyright (c) Zend Technologies
        with Zend OPcache v7.4.14, Copyright (c), by Zend Technologies"

     

    So thats not it .... I have had that problem before and fixed it with an update.

     

    I can still access most of my files through the Nextcloud sync client in Windows so not a complete loss. 

     

    It's got to be with the webui only.... but can't think what that would be since nothing else changed. 

     

    I use reverse proxy for remote access but get the same error when I access locally - so that's not it....

     

    I get the same error in Linux Mint when I try to use the webui ...at least its consistent🙄

     

    Well I'll bump along and noodle on this some more....perhaps there are others that run into the same problem and will wake up the NC folks to the problem.

     

    I left the same post on the NC support forum.

     

    Ill post back if I find a solution ....🤔

     

    Thanks for the responses .... we will figure this out .....

     

    Cheers

     

    Toolmanz

     

    You'll want to be checking your logs. nginx logs within the `/config` mount and also the nextcloud log itself in the root of your `/data` mount. That should give some sort of insight to what's happening.

  12. 36 minutes ago, discojon said:

    So I just started my restored docker and got the same PHP error as before.

     

    
    This version of Nextcloud is not compatible with > PHP 7.3.
    You are currently running 7.4.14.

     

    Current version is 17.0.9. CLI in and ran

     

    
    docker exec -it nextcloud updater.phar

     

    and it is trying to upgrade. "Update to Nextcloud 17.0.10 available. (channel: "stable")".  As with the webupdater, it errors out with this.

     

    
    oot@Tower:~# docker exec -it nextcloud updater.phar
    Nextcloud Updater - version: v16.0.3-3-ga0c2b25 dirty
    
    Current version is 17.0.9.
    
    Update to Nextcloud 17.0.10 available. (channel: "stable")
    Following file will be downloaded automatically: https://download.nextcloud.com/server/releases/nextcloud-17.0.10.zip
    Open changelog ↗
    
    Steps that will be executed:
    [ ] Check for expected files
    [ ] Check for write permissions
    [ ] Create backup
    [ ] Downloading
    [ ] Verify integrity
    [ ] Extracting
    [ ] Enable maintenance mode
    [ ] Replace entry points
    [ ] Delete old files
    [ ] Move new files in place
    [ ] Done
    
    Start update? [y/N] y
    
    Info: Pressing Ctrl-C will finish the currently running step and then stops the updater.
    
    [✔] Check for expected files
    [✔] Check for write permissions
    [✔] Create backup
    
    Update stopped. To resume or retry just execute the updater again.

     

    Looks like someone had the same issue here: https://github.com/nextcloud/mail/issues/2583

    Seems related to the Mail app within nextcloud.

  13. 3 minutes ago, discojon said:

    The config folder is located in your Nextcloud data location.  

     

     

    The only options I'm presented with when updating in the container are stable and beta.  I don't have an option to upgrade to next version

    The nextcloud web updater should offer you newer versions or you can cli into the container and run `updater.phar`

  14. 2 minutes ago, discojon said:

    So I was able to bypass the error message but the subsequent update failed so I'm not recommending that at this point.  I'm currently restoring from a backup and hopefully that will get me running.  I think the core issue here is the version of NC this container is running is 17 which is EoL apparently.  

    This is just wrong - it's because you haven't been updating nextcloud within the container. It's our only one that you have to independently update inside the container aswell images.