Not seeing NC25 as update option

Strange, It appeared for me after I updated to 24.0.8. I’m on PHP8.1

You might want to update to 24.0.8 and then you’ll get the option to update to 25.0.x

1 Like

You may have to update to 24.0.8 first.

Den onsdag 14 december 2022 16:02:46 CET, iamhives via Nextcloud community noreply@nextcloud.com skrev:

| iamhives
December 14 |

  • | - |

Is NC25 available for general use? I’m on the stable channel and only see 24.0.8 in the online update. Even under the beta channel I see the same thing. Looks like 25 is in RC 3 but is 25 generally available and stable? If it is why is it not visible for update via the online update tool?

As others have said, you have to update to the latest v24 version before v25 is offered as an update. I guess this is because they’ve really tested the upgrade with the last v24 version.

1 Like

For those using the docker container, the stable version has been changed to 25.0.2.
I’m on version 24.0.7 and will need to change my docker tag to 24 to update to 24.0.8, before changing back to stable to get the 25.0.2 update.

Hopefully this helps others in my position.

Are you on a 64bit os or 32? I run NC off a RiP and it would only show me 24.x until I switched it to a 64bit os

I’m pretty sure you have to update to the latest version before upgrading to 25.

Thanks everyone. I’ll update to the latest 24.0.8 and then 25. I guess I didn’t see anywhere that that was a necessity but guess that makes sense (I’m not a dev)

1 Like

Hi,

yes, it is a stable verion for generalt use. Updates in NC are step by step.
So you first have to update to 24.0.8 and then you are able to start
the next update to 25.0.2 .

Regards
49,7

25.0.2 isn’t stable even if on docker it is marked as. Many problems with login and menue structure under Mac with all kind of browsers.

2 Likes

For some unknown reason I had the option to upgrade to NC25, on stable channel… I don’t know why, but I did.
It’s kinda nice to see & use the optical and operational features.

I was lucky that I was moving the installation to a new one on a new server, tho I also didn’t get anything for 25 on the older one

I Have the Same Problem Here… I am running on Bare Metal server running Nextcloud-AIO 24.0.8 and I am also not seeing the 25? updates. I even switched over to BETA to try to get it to update.

Running AIO I am not sure what i need to do it push my Server to update?

New to nextcloud so don’t yell to much.

Thanks John

1 Like

Hi, the official NC25 update for AIO is not released yet but you can already update at will by following update to Nextcloud 25 · Issue #1280 · nextcloud/all-in-one · GitHub.

Thanks for the FAST update … I can wait i was just reading about all the switching and did not know why i was not switch yet … thanks again … Release date?

thanks john

No release date yet but it will be included in the next release of AIO.

1 Like

ok well took down frdora 36 server and as you suggested install Ubuntu 22.04 LTS server … I dont like it as i was a Fedora man from the days of redhat.

biw bit getting the same error but i am still having problems, Some things are not starting the way they should … I think

here is the talk log, Let me know what you think?

  • sed -i ‘s|#turn_rest_api_key.*|turn_rest_api_key = “5df9f0e275b5d25bced466464e3196d461796d49d0222b4e”|’ /etc/janus/janus.jcfg
  • sed -i ‘s|#full_trickle.*|full_trickle = true|g’ /etc/janus/janus.jcfg
  • sed -i ‘s|#stun_server.*|stun_server = “127.0.0.1”|g’ /etc/janus/janus.jcfg
  • sed -i ‘s|#stun_port.*|stun_port = 3478|g’ /etc/janus/janus.jcfg
  • sed -i ‘s|#turn_port.*|turn_port = 3478|g’ /etc/janus/janus.jcfg
  • sed -i ‘s|#turn_server.*|turn_server = “127.0.0.1”|g’ /etc/janus/janus.jcfg
  • sed -i ‘s|#turn_type .*|turn_type = “udp”|g’ /etc/janus/janus.jcfg
  • sed -i ‘s|#ice_ignore_list .*|ice_ignore_list = “udp”|g’ /etc/janus/janus.jcfg
  • sed -i ‘s|#interface.*|interface = “lo”|g’ /etc/janus/janus.transport.websockets.jcfg
  • sed -i ‘s|#ws_interface.*|ws_interface = “lo”|g’ /etc/janus/janus.transport.websockets.jcfg
  • sed -i ‘s|certfile =|#certfile =|g’ /etc/janus/janus.transport.mqtt.jcfg
  • sed -i ‘s|keyfile =|#keyfile =|g’ /etc/janus/janus.transport.mqtt.jcfg
  • set +x
    [26] 2023/01/03 03:41:40.157816 [INF] Starting nats-server
    [26] 2023/01/03 03:41:40.157853 [INF] Version: 2.9.10
    [26] 2023/01/03 03:41:40.157855 [INF] Git: [4caf6aa]
    [26] 2023/01/03 03:41:40.157857 [INF] Name: ND4EE6DNWLKMNXXLUR2Z4VSC5YTXAWBPEGBZJBW4HWZU47LURNABYLI2
    [26] 2023/01/03 03:41:40.157859 [INF] ID: ND4EE6DNWLKMNXXLUR2Z4VSC5YTXAWBPEGBZJBW4HWZU47LURNABYLI2
    [26] 2023/01/03 03:41:40.157863 [INF] Using configuration file: /etc/nats/nats.conf
    [26] 2023/01/03 03:41:40.158402 [INF] Listening for client connections on 127.0.0.1:4222
    [26] 2023/01/03 03:41:40.158412 [INF] Server is ready
    main.go:133: Starting up version 33dc5a554b496bd253bedbecc6755de514a64867/go1.19 as pid 27
    main.go:142: Using a maximum of 8 CPUs
    Janus version: 1101 (1.1.1)
    Janus commit: not-a-git-repo
    Compiled on: Thu Dec 8 10:08:48 UTC 2022

natsclient.go:108: Connection established to nats://127.0.0.1:4222 (ND4EE6DNWLKMNXXLUR2Z4VSC5YTXAWBPEGBZJBW4HWZU47LURNABYLI2)
grpc_common.go:167: WARNING: No GRPC server certificate and/or key configured, running unencrypted
grpc_common.go:169: WARNING: No GRPC CA configured, expecting unencrypted connections
backend_storage_static.go:72: Backend backend-1 added for https://n3ovo.org/
hub.go:201: Using a maximum of 8 concurrent backend connections per host
hub.go:208: Using a timeout of 10s for backend connections
Logger plugins folder: /usr/lib/x86_64-linux-gnu/janus/loggers
hub.go:304: Not using GeoIP database
Loading logger plugin ‘libjanus_jsonlog.so’…
[WARN] JSON logger disabled
Adding 1 external loggers

Starting Meetecho Janus (WebRTC Server) v1.1.1

Checking command line arguments…
main.go:228: Could not initialize janus MCU (dial tcp 127.0.0.1:8188: connect: connection refused) will retry in 1s
Debug/log level is 4
Debug/log timestamps are disabled
Debug/log colors are disabled
Adding ‘vmnet’ to the ICE ignore list…
Using 172.17.0.4 as local IP…
Token based authentication disabled
Initializing recorder code
Initializing ICE stuff (Full mode, ICE-TCP candidates disabled, full-trickle, IPv6 support disabled)
STUN server to use: 127.0.0.1:3478

127.0.0.1:3478 (IPv4)
Testing STUN server: message is of 20 bytes
main.go:228: Could not initialize janus MCU (dial tcp 127.0.0.1:8188: connect: connection refused) will retry in 2s
main.go:228: Could not initialize janus MCU (dial tcp 127.0.0.1:8188: connect: connection refused) will retry in 4s
[FATAL] [ice.c:janus_ice_test_stun_server:1095] No response to our STUN BINDING test
[FATAL] [janus.c:main:5108] Invalid STUN address 127.0.0.1:3478
Janus version: 1101 (1.1.1)
Janus commit: not-a-git-repo
Compiled on: Thu Dec 8 10:08:48 UTC 2022

Logger plugins folder: /usr/lib/x86_64-linux-gnu/janus/loggers
Loading logger plugin ‘libjanus_jsonlog.so’…
[WARN] JSON logger disabled
Adding 1 external loggers

Starting Meetecho Janus (WebRTC Server) v1.1.1

Checking command line arguments…
Debug/log level is 4
Debug/log timestamps are disabled
Debug/log colors are disabled
Adding ‘vmnet’ to the ICE ignore list…
Using 172.17.0.4 as local IP…
Token based authentication disabled
Initializing recorder code
Initializing ICE stuff (Full mode, ICE-TCP candidates disabled, full-trickle, IPv6 support disabled)
STUN server to use: 127.0.0.1:3478

127.0.0.1:3478 (IPv4)
Testing STUN server: message is of 20 bytes
main.go:228: Could not initialize janus MCU (dial tcp 127.0.0.1:8188: connect: connection refused) will retry in 8s
Our public address is 127.0.0.1
TURN server to use: 127.0.0.1:3478 (udp)
TURN REST API backend: (disabled)
Crypto: OpenSSL >= 1.1.0
No cert/key specified, autogenerating some…
Fingerprint of our certificate: 24:16:26:DE:03:9F:2E:08:9A:72:00:FC:EC:7C:1D:43:B0:C0:E7:D5:C9:FF:34:2B:02:F2:BB:BF:99:33:E7:CE
Event handlers support disabled
Plugins folder: /usr/lib/x86_64-linux-gnu/janus/plugins
Sessions watchdog started
Joining Janus requests handler thread
Loading plugin ‘libjanus_duktape.so’…
[e[36mechotest.jse[0m] Loading script…
[e[36mechotest.jse[0m] Modules folder: /usr/share/janus/duktape
[e[36mechotest.jse[0m] Loading module: janus-sdp
[e[36mechotest.jse[0m] Module loaded
[e[36mechotest.jse[0m] Script loaded
[e[36mechotest.jse[0m] Initializing…
[e[36mechotest.jse[0m] Initialized
Janus JavaScript plugin (Duktape) initialized!
Loading plugin ‘libjanus_videocall.so’…
JANUS VideoCall plugin initialized!
Loading plugin ‘libjanus_echotest.so’…
JANUS EchoTest plugin initialized!
Loading plugin ‘libjanus_recordplay.so’…
JANUS Record&Play plugin initialized!
Loading plugin ‘libjanus_sip.so’…
JANUS SIP plugin initialized!
Loading plugin ‘libjanus_lua.so’…
e[0m[e[34mechotest.luae[0m]e[0m Loading…
e[0m[e[34mechotest.luae[0m]e[0m Loaded
e[0m[e[34mechotest.luae[0m]e[0m Initializing…
e[0m[e[34mechotest.luae[0m]e[0m Initialized
Janus Lua plugin initialized!
Loading plugin ‘libjanus_nosip.so’…
JANUS NoSIP plugin initialized!
Loading plugin ‘libjanus_audiobridge.so’…
JANUS AudioBridge plugin initialized!
Loading plugin ‘libjanus_textroom.so’…
JANUS TextRoom plugin initialized!
Loading plugin ‘libjanus_voicemail.so’…
JANUS VoiceMail plugin initialized!
Loading plugin ‘libjanus_videoroom.so’…
JANUS VideoRoom plugin initialized!
Loading plugin ‘libjanus_streaming.so’…
[ERR] [plugins/janus_streaming.c:janus_streaming_init:2492] Can’t add ‘live’ mountpoint, no such file ‘/usr/share/janus/streams/radio.alaw’…
[ERR] [plugins/janus_streaming.c:janus_streaming_init:2566] Can’t add ‘ondemand’ mountpoint, no such file ‘/usr/share/janus/streams/music.mulaw’…
JANUS Streaming plugin initialized!
Transport plugins folder: /usr/lib/x86_64-linux-gnu/janus/transports
Loading transport plugin ‘libjanus_http.so’…
HTTP transport timer started
HTTP webserver started (port 8088, /janus path listener)…
JANUS REST (HTTP/HTTPS) transport plugin initialized!
Loading transport plugin ‘libjanus_nanomsg.so’…
JANUS Nanomsg transport plugin initialized!
Loading transport plugin ‘libjanus_mqtt.so’…
Nanomsg thread started
MQTT SSL support disabled
[WARN] MQTT support disabled for both Janus and Admin API, giving up
JANUS MQTT transport plugin destroyed!
[WARN] The ‘janus.transport.mqtt’ plugin could not be initialized
Loading transport plugin ‘libjanus_pfunix.so’…
[WARN] No Unix Sockets server started, giving up…
[WARN] The ‘janus.transport.pfunix’ plugin could not be initialized
Loading transport plugin ‘libjanus_rabbitmq.so’…
RabbitMQ SSL support disabled
[WARN] RabbitMQ support disabled for both Janus and Admin API, giving up
[WARN] The ‘janus.transport.rabbitmq’ plugin could not be initialized
Loading transport plugin ‘libjanus_websockets.so’…
libwebsockets logging: 0
Websockets server started (port 8188)…
JANUS WebSockets transport plugin initialized!
WebSockets thread started
mcu_janus.go:294: Connected to Janus WebRTC Server 1.1.1 by Meetecho s.r.l.
mcu_janus.go:300: Found JANUS VideoRoom plugin 0.0.9 by Meetecho s.r.l.
mcu_janus.go:305: Data channels are supported
mcu_janus.go:309: Full-Trickle is enabled
mcu_janus.go:311: Maximum bandwidth 1048576 bits/sec per publishing stream
mcu_janus.go:312: Maximum bandwidth 2097152 bits/sec per screensharing stream
Creating new session: 3173686510448706; 0x7f8798006a40
mcu_janus.go:318: Created Janus session 3173686510448706
Creating new handle in session 3173686510448706: 7999340553367163; 0x7f8798006a40 0x7f8798003120
mcu_janus.go:325: Created Janus handle 7999340553367163
main.go:263: Using janus MCU
hub.go:386: Using a timeout of 10s for MCU requests
backend_server.go:95: Using configured TURN API key
backend_server.go:96: Using configured shared TURN secret
backend_server.go:98: Adding “turn:n3ovo.org:3478?transport=tcp” as TURN server
backend_server.go:98: Adding “turn:n3ovo.org:3478?transport=udp” as TURN server
backend_server.go:105: No IPs configured for the stats endpoint, only allowing access from 127.0.0.1
main.go:339: Listening on 0.0.0.0:8081


Thanks John

Since you are reaching this now it looks correctly started. Have you opened the for talk needed tcp and udp ports in your firewall/router?

yes i have but the light is still yellow ??

Hm, that is indeed very strange. Is it the only container that is still yellow?