j0nnymoe
-
Posts
353 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by j0nnymoe
-
-
1 hour ago, Pope Viper said:
Just performed the latest updated, and while it seemed successful and the container came back up, I'm unable to attach to the plex server.
Where can I start looking?
Thanks!
Check both container logs and your plex logs within your appdata.
-
21 hours ago, Reva said:
I'm getting this error when in the Nextcloud WebUi trying to create an admin account and configuring MariaDB: Error while trying to create admin user: Failed to connect to the database: An exception occurred in the driver: SQLSTATE[HY000] [1045] Access denied for user '******'@'172.19.0.1' (using password: YES)
Why is this happening?
That's saying it's unable to connect to your mariadb instance. So re-check your mariadb container is working correctly.
-
41 minutes ago, kralwal said:
Hey guys
it seems like my docker container got nuked with the latest update. I think it’s related to my Mariadb. My Mariadb log gets spammed with the same message over and over
in the named file its just this message over and over again:
can I just delete my Mariadb docker and reinstall it without completely destroying my Nextcloud installation?If you search back through this post or the mariadb thread, you'll see solutions to fix it.
-
On 10/23/2021 at 4:57 PM, ebnerjoh said:
Hi,
Today I updated the MariaDB Docker and now it is not starting anymore.
the err-log shows the following:
2021-10-23 17:53:53 0 [ERROR] Found 1 prepared transactions! It means that mysqld was not shut down properly last time and critical recovery information (last binlog or tc.log file) was manually deleted after a crash. You have to start mysqld with --tc-heuristic-recover switch to commit or rollback pending transactions. 2021-10-23 17:53:53 0 [ERROR] Aborting
any ideas?Br,
Johannes
40 minutes ago, Pixel5 said:my mariaDB is stuck in a boot loop now, is anyone else having this problem after the lastest update?
211026 11:00:22 mysqld_safe Starting mariadbd daemon with databases from /config/databasesThis has already been heavily discussed with solutions in previous posts of this thread.
-
On 10/2/2021 at 1:53 PM, trevaaaaaaa said:
I was going to try this but I don't have a mariadb directory in /var/run/s6/services/ of my nextcloud container.
Because it's not in the nextcloud container, it's in the mariadb container.
-
Just to make it clear, if anyone is having issues with the update to the latest version of mariadb. It's due to your database corrupting as your previous container wasn't shutdown cleanly (Something using during an update / automatic updates killing the container early). To recover your database, do the following with -all- containers that use mariadb off:
Try the `linuxserver/mariadb:version-110.4.21mariabionic` tag, let everything start up, check the logs to make sure it's all clean, then do `docker exec nextclouddb s6-svc -d /var/run/s6/services/mariadb/` (assuming your container is called nexclouddb, otherwise adjust that appropriately). Wait ~30 seconds and then stop the container and update to latest.
If this doesn't work, you will need to restore a working backup.
-
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.
-
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.
-
1
-
-
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.
-
18 hours ago, sonic6 said:
here is my workaround,
try using this
Repository: linuxserver/mariadb:110.4.21mariabionic-ls31
Be aware that this will no longer get updates.
-
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?
-
1
-
-
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.
-
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.
-
The error shouldn't stop the controller from working itself but it's something to wait for unifi to fix.
-
I would highly suggest users having issues with this find a better solution, as I mentioned here:
-
29 minutes ago, dfox1787 said:
Still no help to get this fixed? anyone please
We can't fix an isse that's related to upstream.
-
3 hours ago, hundsboog said:
No updates yet? Its not working anymore... Did a complete reinstall, but unfortunately when it starts OCR'ing, nothing further happens. 😕
I really liked it
Some more info on what you've done might help
-
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-indicesAnd 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.
-
1
-
-
3 hours ago, 007craft said:
Jellyfin 10.7.0 was released a couple days ago but Unraid is not prompting for an update and Jellyfin is still on 10.6.4
The container was updated a couple hours after it was released
-
5 hours ago, Kira said:
Is ls.io going to update the controller version to 6.1.61 ?
When it's released yes. (And that means when they publish it to their apt-get repo, not just on their forum/blog.)
-
Unfortunately, the state of this container currently is that it's a lottery if it will work for you.
There has been a long standing issue with this container: https://github.com/linuxserver/docker-openvpn-as/issues/113 everything is explained there.
In short, if you have issues with this container, I personally would suggest not wasting time on this and finding a better solution.
-
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 👍
-
5 hours ago, Abzstrak said:
anyone getting the option to upgrade to 21? Mine is at 20.0.7 and showing no updates available. I tried beta, but that only offered 20.0.8 RC...
If it's an existing install, you won't get offered the update until Nextcloud release the OTA's.
-
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.
[Support] Linuxserver.io - Nextcloud
in Docker Containers
Posted
"MySQL server has gone away in /config/www/nextcloud/lib/private/DB/Connection.php:87"
You need to investigate your MariaDB/MySQL Container as the problem lies there, not with nextcloud.