gevsan

September 10

2 minutes ago, ich777 said:

Thanks for letting me know, so only host network and removing -multihome is the way to go for now until CoffeeStain releases a fix for that.

Not working for me either. I only have 1 nic in the system and before I was using a Custom network.

Now I have tried to delete the container and re-installed it again. Changed to Host and removed -multihome 0.0.0.0 from the Game Parameters:

Still not working tho

September 10

4 minutes ago, ich777 said:

Set the network as mentioned here:

Yes, i changed to Host

Command execution
docker run
  -d
  --name='Satisfactory'
  --net='host'
  -e TZ="Europe/Berlin"
  -e HOST_OS="Unraid"
  -e HOST_HOSTNAME="Tower"
  -e HOST_CONTAINERNAME="Satisfactory"
  -e 'GAME_ID'='1690800'
  -e 'UDP_PORT_7777'='7777'
  -e 'GAME_PARAMS'='-log
  -unattended'
  -e 'VALIDATE'=''
  -e 'UID'='99'
  -e 'GID'='100'
  -e 'UMASK'='0000'
  -e 'USERNAME'=''
  -e 'PASSWRD'=''
  -l net.unraid.docker.managed=dockerman
  -l net.unraid.docker.icon='https://raw.githubusercontent.com/ich777/docker-templates/master/ich777/images/satisfactory.png'
  -v '/mnt/user/appdata/steamcmd':'/serverdata/steamcmd':'rw'
  -v '/mnt/cache_doc/appdata/satisfactory':'/serverdata/serverfiles':'rw'
  --restart=unless-stopped 'ich777/steamcmd:satisfactory'
da8788fdafcd7620ca82fd393b03797819c0a7512ccd002e1a42f0e4402b79d2

The command finished successfully!

Im still getting the "Failed to connect to the Server API"

September 10

2 minutes ago, ich777 said:

Please double check, that doesn't fix it for me, the actual problem is that the http api binds to the loopback interface so to speak 127.0.0.1 and not 0.0.0.0 so it will not work properly, I assume if you change the network mode to br0 or host that it will work but this is not the recommended way of doing it.

Removing multihome did not work for me either.

August 9

Okay, so If anyone got the same issue..

I saved the 7d2d /user folder and my "renamed" serverconfig.xml then deleted the whole docker and image from the disk.

Reinstalled, started and waited for everything to download. The stopped and changed the serverconfig file in the container and replaced the existing /user folder with the one I saved before.

Now it's back on v.1.0

August 8

30 minutes ago, Spectral Force said:

Check out my guide.

https://7dac.net/a-guide-on-how-to-install-ich777s-container-docker-on-an-unraid-server/

To answer your question, copy/paste, rename serverconfig.xml, match name in container template.

Okay I now have a renamed config file and it stays unedited. Thanks!

But the problem with my server still being on version 1.1 persists.

Im using 294420 and validate:true

What am I doing wrong?

August 8

10 minutes ago, Spectral Force said:

After you took out the -beta latest_experimental did you restart the container to redownload the files? If yes, put True in validation & try again.

Yes, i restarted and it did redownload the files.

after i put "true" in validation it redownload a new serverconfig everytime. If I Edit something in the config and restart the container i get a new "default" serverconfig.

How do I keep my serverconfig?

August 8

21 minutes ago, Spectral Force said:

For stable you do not put anything in. Just the appid, which Ich already has in place.

Hey Spectral Force,

Thanks for the reply.

I'm using 294420 right now and this is what i get ingame:

Any ideas?

August 8

Hey Ich777.

I have a small problem with 7d2d.

There was an update recently, so my server updated to version 1.1 which is experimental.

But I want to stay on version 1.0

I was using GAME_ID: 294420

So if i want to stay on version 1.0 I should use the GAME_ID below?

GAME_ID: 294420 -beta stable_v1.0

But in the logs it says: ERROR! Failed to set beta 'stable_v1.0'

Command execution
docker run
  -d
  --name='7DaysToDie'
  --net='lokarna'
  -e TZ="Europe/Berlin"
  -e HOST_OS="Unraid"
  -e HOST_HOSTNAME="Tower"
  -e HOST_CONTAINERNAME="7DaysToDie"
  -e 'GAME_ID'='294420
  -beta stable_v1.0'
  -e 'SERVERCONFIG'='serverconfig.xml'
  -e 'GAME_PARAMS'='-logfile 7DaysToDie_Data/output_log.txt $@'
  -e 'VALIDATE'=''
  -e 'ENABLE_BEPINEX'='false'
  -e 'USERNAME'=''
  -e 'PASSWRD'=''
  -e 'UID'='99'
  -e 'GID'='100'
  -l net.unraid.docker.managed=dockerman
  -l net.unraid.docker.icon='https://raw.githubusercontent.com/ich777/docker-templates/master/ich777/images/7dtd.png'
  -p '26900:26900/tcp'
  -p '26900:26900/udp'
  -p '26901:26901/udp'
  -p '26902:26902/udp'
  -p '26903:26903/udp'
  -p '8383:8080/tcp'
  -p '8082:8082/tcp'
  -p '27015:27015/udp'
  -v '/mnt/user/appdata/steamcmd':'/serverdata/steamcmd':'rw'
  -v '/mnt/cache_doc/appdata/7dtd':'/serverdata/serverfiles':'rw'
  --restart=unless-stopped 'ich777/steamcmd:7dtd'
e90b77a48defa3e1453acd8ab98c7bb7f70a927377a7d9a88773ff998d9522eb

The command finished successfully!

LOGS:

---Ensuring UID: 99 matches user---
---Ensuring GID: 100 matches user---
---Setting umask to 000---
---Checking for optional scripts---
---No optional script found, continuing---
---Taking ownership of data...---
---Starting...---
---Update SteamCMD---
Redirecting stderr to '/serverdata/Steam/logs/stderr.txt'
Logging directory: '/serverdata/Steam/logs'
[  0%] Checking for available updates...
[----] Verifying installation...
UpdateUI: skip show logoSteam Console Client (c) Valve Corporation - version 1721172922
-- type 'quit' to exit --
Loading Steam API...OK

Connecting anonymously to Steam Public...OK
Waiting for client config...OK
Waiting for user info...OK
---Update Server---
Redirecting stderr to '/serverdata/Steam/logs/stderr.txt'
Logging directory: '/serverdata/Steam/logs'
[  0%] Checking for available updates...
[----] Verifying installation...
UpdateUI: skip show logoSteam Console Client (c) Valve Corporation - version 1721172922
-- type 'quit' to exit --
Loading Steam API...OK

Connecting anonymously to Steam Public...OK
Waiting for client config...OK
Waiting for user info...OK
ERROR! Failed to set beta 'stable_v1.0'
---Prepare Server---
---UserDataFolder location correct---
---UserDataFolder location found---
---Server ready---
---Start Server---
[UnityMemory] Configuration Parameters - Can be set up in boot.config
    "memorysetup-bucket-allocator-granularity=16"
    "memorysetup-bucket-allocator-bucket-count=8"
    "memorysetup-bucket-allocator-block-size=4194304"
    "memorysetup-bucket-allocator-block-count=1"
    "memorysetup-main-allocator-block-size=16777216"
    "memorysetup-thread-allocator-block-size=16777216"
    "memorysetup-gfx-main-allocator-block-size=16777216"
    "memorysetup-gfx-thread-allocator-block-size=16777216"
    "memorysetup-cache-allocator-block-size=4194304"
    "memorysetup-typetree-allocator-block-size=2097152"
    "memorysetup-profiler-bucket-allocator-granularity=16"
    "memorysetup-profiler-bucket-allocator-bucket-count=8"
    "memorysetup-profiler-bucket-allocator-block-size=4194304"
    "memorysetup-profiler-bucket-allocator-block-count=1"
    "memorysetup-profiler-allocator-block-size=16777216"
    "memorysetup-profiler-editor-allocator-block-size=1048576"
    "memorysetup-temp-allocator-size-main=4194304"
    "memorysetup-job-temp-allocator-block-size=2097152"
    "memorysetup-job-temp-allocator-block-size-background=1048576"
    "memorysetup-job-temp-allocator-reduction-small-platforms=262144"
    "memorysetup-allocator-temp-initial-block-size-main=262144"
    "memorysetup-allocator-temp-initial-block-size-worker=262144"
    "memorysetup-temp-allocator-size-background-worker=32768"
    "memorysetup-temp-allocator-size-job-worker=262144"
    "memorysetup-temp-allocator-size-preload-manager=262144"
    "memorysetup-temp-allocator-size-nav-mesh-worker=65536"
    "memorysetup-temp-allocator-size-audio-worker=65536"
    "memorysetup-temp-allocator-size-cloud-worker=32768"
    "memorysetup-temp-allocator-size-gfx=262144"

June 25

Hey,

I tried to restore a folder but im getting "The selected source seems invalid."

Debug ID: 22b8f4c9-bf51-451b-842b-c62a9226fccb

image.png.f155a6abd18c242f78dfb29d818ac94a.png image.png.3391a746fbde6fab361927aaedfe0756.png

June 17

2 minutes ago, ich777 said:

The answer is simple, please don‘t fill in Steam credentials.

Steam credentials are only required if they are not hidden away at the Show more settings… section and marked with the red asterisk!

Thanks!

June 17

Hello!

I have a problem with KillingFloor 2.

Says in log "ERROR! Failed to install app '232130' (No subscription)"

What can I do?

This is the LOG:

---Prepare Server---
---Start Server---
---Ensuring UID: 99 matches user---
usermod: no changes
---Ensuring GID: 100 matches user---
usermod: no changes
---Setting umask to 000---
---Checking for optional scripts---
---No optional script found, continuing---
---Taking ownership of data...---
---Starting...---
---Update SteamCMD---
Redirecting stderr to '/serverdata/Steam/logs/stderr.txt'
Logging directory: '/serverdata/Steam/logs'
[  0%] Checking for available updates...
[----] Verifying installation...
Steam Console Client (c) Valve Corporation - version 1718305764
-- type 'quit' to exit --
Loading Steam API...OK
Logging in user '???' to Steam Public...OK
Waiting for client config...OK
Waiting for user info...OK
---Update Server---
Redirecting stderr to '/serverdata/Steam/logs/stderr.txt'
Logging directory: '/serverdata/Steam/logs'
[  0%] Checking for available updates...
[----] Verifying installation...
Steam Console Client (c) Valve Corporation - version 1718305764
-- type 'quit' to exit --
Loading Steam API...OK
Logging in user '???' to Steam Public...OK
Waiting for client config...OK
Waiting for user info...OK
ERROR! Failed to install app '232130' (No subscription)

Template:

docker run
  -d
  --name='KillingFloor2'
  --net='bridge'
  -e TZ="Europe/Berlin"
  -e HOST_OS="Unraid"
  -e HOST_HOSTNAME="Tower"
  -e HOST_CONTAINERNAME="KillingFloor2"
  -e 'GAME_ID'='232130'
  -e 'GAME_PARAMS'='kf-bioticslab'
  -e 'VALIDATE'='VALIDATE'
  -e 'USERNAME'='???'
  -e 'PASSWRD'='???'
  -e 'UID'='99'
  -e 'GID'='100'
  -l net.unraid.docker.managed=dockerman
  -l net.unraid.docker.icon='https://raw.githubusercontent.com/ich777/docker-templates/master/ich777/images/killingfloor2.png'
  -p '8888:7777/udp'
  -p '27016:27015/udp'
  -p '8083:8080/tcp'
  -p '20560:20560/udp'
  -v '/mnt/user/appdata/steamcmd':'/serverdata/steamcmd':'rw'
  -v '/mnt/cache_doc/appdata/killingfloor2':'/serverdata/serverfiles':'rw'
  --restart=unless-stopped 'ich777/steamcmd:killingfloor2'
da8cb987d55dae0917672de49ff9589231cf116eb6f10997ee0afd5350d01771

The command finished successfully!

November 9, 2023

Solved.

My switchdied somehow..

I just restarted the switch and my server was back online.

Thanks everyone!

November 9, 2023

46 minutes ago, JorgeB said:
Nov  8 21:19:44 Tower kernel: NETDEV WATCHDOG: eth0 (r8169): transmit queue 0 timed out
Possibly a NIC issue, try rebooting.

Hey,

I did try to reboot first. After the reboot i took the diagnostics that are in my first post.

Also, before going to work this morning I tried to start up the server again but with the same issue

So totally i've restarted the server 3 times now.

Could it be the NIC on the mobo that are dead?

November 8, 2023

Hello,

I can't acces the web gui from my LAN.

It worked fine some hours ago. I have not installed or changed anything on my server the last 1 or 2 weeks..

I can't access my dockers either. So i assume that something is wrong.

But I can acces the "shell".

Could anyone check my diagnostics?

I had similare issues a while ago when my boot-USB died.

Maybe my new drive also died?

Thanks..

/G

tower-diagnostics-20231108-2129.zip

September 11, 2023

On 4/21/2023 at 12:31 PM, JorgeB said:

There's only one, so if you have a backup restore, if you don't you can recreate the VM with the same settings and point to the existing vdisk.

Hey, I'm sorry for the insanely long delay for reply

I did find backup but i'm not sure if it's working...

- How do I replace my existing libvirt file with my backup?

- Do I have to worry about my dockers when doing this?

August 2, 2023

Hello.

I can't get Tachideck to download as cbz.

Also I can't get the authorization to work.

Here is my docker run and template.

image.png.8bda88bbff98344710dc2920add81a70.png

April 26, 2023

I had problems with my Redis docker but got it to work again.

Now i'm getting this error in the log.

2023/04/26 15:07:16 [error] 324#324: *566 FastCGI sent in stderr: "PHP message: PHP Fatal error:  Cannot declare class OC\Memcache\Redis, because the name is already in use in /config/www/nextcloud/lib/private/Memcache/Redis.php on line 34" while reading response header from upstream, client: 162.158.222.183, server: _, request: "GET /status.php HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "mydomain"
2023/04/26 15:07:43 [error] 318#318: *1 FastCGI sent in stderr: "PHP message: PHP Fatal error:  Cannot declare class OC\Memcache\Redis, because the name is already in use in /config/www/nextcloud/lib/private/Memcache/Redis.php on line 34" while reading response header from upstream, client: 162.158.222.228, server: _, request: "POST /login HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "mydomain"
2023/04/26 15:07:48 [error] 319#319: *3 FastCGI sent in stderr: "PHP message: PHP Fatal error:  Cannot declare class OC\Memcache\Redis, because the name is already in use in /config/www/nextcloud/lib/private/Memcache/Redis.php on line 34" while reading response header from upstream, client: 162.158.222.228, server: _, request: "POST /login HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "mydomain"

/config/www/nextcloud/lib/private/Memcache/Redis.php

line 34

class Redis extends Cache implements IMemcacheTTL {
	/**
	 * @var \Redis $cache
	 */
	private static $cache = null;

	public function __construct($prefix = '', string $logFile = '') {
		parent::__construct($prefix);
		if (is_null(self::$cache)) {
			self::$cache = \OC::$server->getGetRedisFactory()->getInstance();
		}
	}

Anyone know what I should do?

April 25, 2023

On 4/25/2023 at 2:03 PM, cat2devnull said:

So first just make sure you are on php 8 as 24.0.12 can't run on php 7.

Run "php -v" from within the docker.

The log files of interest are;

/config/log/php/error.log

/config/log/nginx/access.log
/config/log/nginx/error.log

This is probably a permissions issue... But that's an educated guess.

See if there are any errors in the logs.

Sorry this is taking so much back and forth but I have never hit this type of corruption during an upgrade and I'm not an expert. I know just enough to be dangerous.
If anyone else on this forum knows what their doing, feel free to jump in.

php -v

root@c9defde43c12:/# php -v
PHP 8.1.18 (cli) (built: Apr 13 2023 23:14:07) (NTS)
Copyright (c) The PHP Group
Zend Engine v4.1.18, Copyright (c) Zend Technologies
    with Zend OPcache v8.1.18, Copyright (c), by Zend Technologies

I've attached the logs.

/config/log/nginx/error.log <-- This is Blank empty.

April 25, 2023

1 hour ago, cat2devnull said:

Worth a shot.

So what does "occ status" think now?

And what version is it trying to update to?

Also you could try performing "occ integrity:check-core" and "occ maintenance:repair" to see if it can fix the issue.

You could also try performing the upgrade via the command line, you might get some more useful debugging. "occ upgrade"

occ status

root@c9defde43c12:/# occ status
Nextcloud or one of the apps require upgrade - only a limited number of commands are available
You may use your browser or the occ upgrade command to do the upgrade
  - installed: true
  - version: 23.0.12.2
  - versionstring: 23.0.12
  - edition: 
  - maintenance: false
  - needsDbUpgrade: true
  - productname: Nextcloud
  - extendedSupport: false
root@c9defde43c12:/# cat /config/www/nextcloud/version.php
<?php 
$OC_Version = array(23,0,12,2);
$OC_VersionString = '23.0.12';
$OC_Edition = '';
$OC_Channel = 'stable';
$OC_VersionCanBeUpgradedFrom = array (
  'nextcloud' => 
  array (
    '22.0' => true,
    '23.0' => true,
  ),
  'owncloud' => 
  array (
    '10.11' => true,
  ),
);
$OC_Build = '2023-03-21T09:23:03+00:00 62cfd3b4c9ff4d8cdbbe6dcc8b63a1085bb94e3d';
$vendor = 'nextcloud';
root@c9defde43c12:/# cat /config/www/nextcloud/config/config.php | grep version
  'version' => '23.0.12.2',

occ integrity:check-core

root@c9defde43c12:/# occ integrity:check-core
Nextcloud or one of the apps require upgrade - only a limited number of commands are available
You may use your browser or the occ upgrade command to do the upgrade
  - INVALID_HASH:
    - version.php:
      - expected: 496b0d7d08003a9eddf37370e7ec64e701f1ea31eaef04d3c26beb1f5777855f608bc436525868473f69d8356b8341a8d3c8ce72830a9f9366643fa7e7c924e8
      - current: bfd86c89b63342ba16e67f0c3488a69e03e08b37c490e8d4dd0bec9112e39fc28a6f00ee261d733bad5afc44bf1d3270a1de1a5e3b1d8defc49eb29f22c0cb2a

occ maintenance:repair

Did not help

occ upgrade

root@c9defde43c12:/# occ upgrade
Nextcloud or one of the apps require upgrade - only a limited number of commands are available
You may use your browser or the occ upgrade command to do the upgrade
Setting log level to debug
Turned on maintenance mode
Updating database schema
Updated database
UnexpectedValueException: The files of the app "files" were not correctly replaced before running the update
Update failed
Maintenance mode is kept active
Resetting log level

Repository: lscr.io/linuxserver/nextcloud:latest

But after this I did try

docker exec -it nextcloud updater.phar

And this actually worked!

Now im back at my login screen, but when im trying to login im getting this error:

“Internal Server Error
The server was unable to complete your request.
If this happens again, please send the technical details below to the server administrator.
More details can be found in the server log"

Im not sure where I can find this log.

I've been looking in the "error.log" but that wasn't much of help..

Worth mentioning,

Now when I am getting to the login screen I did run these command again:

root@c9defde43c12:/# occ status
  - installed: true
  - version: 24.0.12.1
  - versionstring: 24.0.12
  - edition: 
  - maintenance: false
  - needsDbUpgrade: false
  - productname: Nextcloud
  - extendedSupport: false
root@c9defde43c12:/# cat /config/www/nextcloud/version.php
<?php 
$OC_Version = array(24,0,12,1);
$OC_VersionString = '24.0.12';
$OC_Edition = '';
$OC_Channel = 'stable';
$OC_VersionCanBeUpgradedFrom = array (
  'nextcloud' => 
  array (
    '23.0' => true,
    '24.0' => true,
  ),
  'owncloud' => 
  array (
    '10.5' => true,
  ),
);
$OC_Build = '2023-04-19T16:04:20+00:00 5b79bb15b510f52ab598fa45e6977857a9d4895a';
$vendor = 'nextcloud';
root@c9defde43c12:/# cat /config/www/nextcloud/config/config.php | grep version
  'version' => '24.0.12.1',

April 24, 2023

3 hours ago, cat2devnull said:
Don't take the blog to literally. It was just meant to be a basic guide.

The blog was written for a docker that doesn't come with a text editor and he is showing how to install nano. The linuxserver.io docker includes nano and vi already. Just use which ever text editor you are more comfortable with.

The main thing is that you need to edit your version.php file to look like;
<?php 
$OC_Version = array(23,0,12,2);
$OC_VersionString = '23.0.12';
$OC_Edition = '';
$OC_Channel = 'stable';
$OC_VersionCanBeUpgradedFrom = array (
  'nextcloud' => 
  array (
    '22.0' => true,
    '23.0' => true,
  ),
  'owncloud' => 
  array (
    '10.11' => true,
  ),
);
$OC_Build = '2023-03-21T09:23:03+00:00 62cfd3b4c9ff4d8cdbbe6dcc8b63a1085bb94e3d';
$vendor = 'nextcloud';
Now restart the docker and see if you can get back into the GUI. It should all be happy now and offer an upgrade to 24.x

Thank you so much for the help.

I did what you explained, and this is what my version.php looks like now

<?php 
$OC_Version = array(23,0,12,2);
$OC_VersionString = '23.0.12';
$OC_Edition = '';
$OC_Channel = 'stable';
$OC_VersionCanBeUpgradedFrom = array (
  'nextcloud' => 
  array (
    '22.0' => true,
    '23.0' => true,
  ),
  'owncloud' => 
  array (
    '10.11' => true,
  ),
);
$OC_Build = '2023-03-21T09:23:03+00:00 62cfd3b4c9ff4d8cdbbe6dcc8b63a1085bb94e3d';
$vendor = 'nextcloud';

Unfortunately it wasn't that "easy"

Im now getting this message..

April 24, 2023

23 minutes ago, cat2devnull said:
So I have not hit this myself but it looks like NextCloud is either trying to upgrade or downgrade in an unsupported way. It is normally only allowed to upgrade one major release at a time.

Eg if it is currently on 22.x.x then it can go to 23.x.x but not to 24.x.x or higher.

This usually happens when it gets confused because of a failed upgrade attempt in the passed so it thinks it is on a higher version than it actually is.

Eg it thinks it's on 25.x and wants to upgrade to 26.x but it actually is on 24.x

Check what version of NextCloud the GUI thinks it is on and what it wants to upgrade to.

This can be seen on the administration overview page (like I posted yesterday).

Then go into the docker shell and run the command "occ status". You should see something like;
root@1384826c6432:/# occ status
  - installed: true
  - version: 25.0.5.1
  - versionstring: 25.0.5
  - edition: 
  - maintenance: false
  - needsDbUpgrade: false
  - productname: Nextcloud
  - extendedSupport: false
Then check what the version.php thinks;
root@1384826c6432:/# cat /config/www/nextcloud/version.php 
<?php 
$OC_Version = array(25,0,5,1);
$OC_VersionString = '25.0.5';
$OC_Edition = '';
$OC_Channel = 'stable';
$OC_VersionCanBeUpgradedFrom = array (
  'nextcloud' => 
  array (
    '24.0' => true,
    '25.0' => true,
  ),
  'owncloud' => 
  array (
    '10.11' => true,
  ),
);
$OC_Build = '2023-03-23T12:04:47+00:00 28add7e896b24fee2714b21a12151e4042ab677c';
$vendor = 'nextcloud';
Also check what version the config file thinks;
root@1384826c6432:/# cat /config/www/nextcloud/config/config.php | grep version
  'version' => '25.0.5.1',
All of these should be in agreement. I suspect that they are not because of a previous failed install.

I would guess that you are actually on 23.x or 24.x but the installer thinks you are on 25.x and it trying to take you straight to 26.0

You need to bring them all back so the system thinks it's on the correct version then it should be happy to upgrade and all going well, no further problems. Here is a blog that walks through the issue. Just keep in mind that since you are using the LinuxServer.io docker the path to the files above is slightly different than what is in the blog. Also it is possible depending on what version you are going from, you might need downgrade the docker by using a specific docker tag, but I wouldn't do that unless you hit a problem.

NextCloud have some nice instructions on the normal upgrade process if you want to get your head around it.

Thanks for the explanation! I get the problem now.

This is what it looks like for me:

root@c9defde43c12:/# occ status
Nextcloud or one of the apps require upgrade - only a limited number of commands are available
You may use your browser or the occ upgrade command to do the upgrade
  - installed: true
  - version: 26.0.0.11
  - versionstring: 26.0.0
  - edition: 
  - maintenance: false
  - needsDbUpgrade: true
  - productname: Nextcloud
  - extendedSupport: false

root@c9defde43c12:/# cat /config/www/nextcloud/version.php
<?php 
$OC_Version = array(26,0,0,11);
$OC_VersionString = '26.0.0';
$OC_Edition = '';
$OC_Channel = 'stable';
$OC_VersionCanBeUpgradedFrom = array (
  'nextcloud' => 
  array (
    '25.0' => true,
    '26.0' => true,
  ),
  'owncloud' => 
  array (
    '10.11' => true,
  ),
);
$OC_Build = '2023-03-21T09:23:03+00:00 62cfd3b4c9ff4d8cdbbe6dcc8b63a1085bb94e3d';
$vendor = 'nextcloud';

root@c9defde43c12:/# cat /config/www/nextcloud/config/config.php | grep version
  'version' => '23.0.12.2',

Now if I follow the Blog, I get stuck on second step...

I don't realy know what this means or how I should do it

docker-compose nextcloud-php apt-get update \
    && apt-get install nano \
    && nano config/config.php

April 24, 2023

20 hours ago, cat2devnull said:

That looks fine.

It's just warning you that it might timeout due to the size of the update.

I have found that can happen but you just re-run the update and it continues where it left off.

Just give it a try or you can perform the update from the command line which should work now that you have updated to docker.

The problem is that I don't know how to proceed from this message..

If i press "Start Upgrade" I will get this error, "Exception: Updates between multiple major versions and downgrades are unsupported."

April 23, 2023

16 minutes ago, cat2devnull said:

This is what happens when you upgrade NextCloud (so it needs a newer PHP 8.x) but don't upgrade the docker (has old PHP 7.x).

Which docker are you running and what version?

It sounds like you are stuck on an old version.

Make sure your tag is set to "latest".

I see..

I changed to "lscr.io/linuxserver/nextcloud:latest"

Now when i acces nextcloud I'm getting this message

April 23, 2023

1 hour ago, cat2devnull said:

This is taken from a post I did in Feb which was about the same issue of PHP and NextCould being out of sync...

Unlike most docker software, upgrading the docker does not upgrade NextCloud itself. NextCloud needs to be upgraded from within its own web interface. (Click on "administration settings" in your profile icon in the top right corner of your Home Screen. That should take you to the Administration Overview link in the left hand toolbar. Scroll down and you should see an Update heading. See the attached image.)

I suspect that you have not upgraded NextCloud in such a long time that the docker environment and the software are now too far out of sync to be compatible.
Probably the easiest fix would be to downgrade your docker. Then from the NextCloud web interface, you can upgrade to the latest and then upgrade the docker again.
You can manually set the repository from within the docker settings.
Try going back to the docker for 24.0.6 from a few months ago.
If you are using the docker from linuxserver.io then you can see all the available tags on their page.
Just edit the NextCloud docker un Unraid and change the repository line to read lscr.io/linuxserver/nextcloud:<tag> where <tag> is the version you want to roll back to. Once you are done, just set it back to "latest".

I would love to try this!

However even if i try to acces nextcloud from domain or local I allways get this message:

This version of Nextcloud requires at least PHP 8.0
You are currently running 7.4.26. Please update your PHP version.

Do you know how to get to the "administarion settings" another way?

April 22, 2023

4 hours ago, MrGrey said:

Have you tried GUI upgrade? Just clutching at straws...

MrGrey.

Hey, I'm not really sure of what you mean?

How do I upgrade the GUI?

gevsan

Posts

Joined

Last visited

Content Type

Profiles

Forums

Downloads

Store

Gallery

Posts posted by gevsan

[Support] ich777 - Gameserver Dockers

[Support] ich777 - Gameserver Dockers

[Support] ich777 - Gameserver Dockers

[Support] ich777 - Gameserver Dockers

[Support] ich777 - Gameserver Dockers

[Support] ich777 - Gameserver Dockers

[Support] ich777 - Gameserver Dockers

[Support] ich777 - Gameserver Dockers

[Plugin] Appdata.Backup

[Support] ich777 - Gameserver Dockers

[Support] ich777 - Gameserver Dockers

Can't acces unraid from LAN

Can't acces unraid from LAN

Can't acces unraid from LAN

Lost my VM

Tachidesk-Docker Support Thread

[Support] Linuxserver.io - Nextcloud

[Support] Linuxserver.io - Nextcloud

[Support] Linuxserver.io - Nextcloud

[Support] Linuxserver.io - Nextcloud

[Support] Linuxserver.io - Nextcloud

[Support] Linuxserver.io - Nextcloud

[Support] Linuxserver.io - Nextcloud

[Support] Linuxserver.io - Nextcloud

[Support] Linuxserver.io - Nextcloud