Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Apps | Demo | Docs | Install
T

TLeM4

@TLeM4
About
Posts
6
Topics
1
Shares
0
Groups
0
Followers
0
Following
0

Posts

Recent Best Controversial

  • Auto-Update to 8.0.3 - systemd-resolved empty response
    T TLeM4

    Thanks, it's working !

    Support update dns

  • Auto-Update to 8.0.3 - systemd-resolved empty response
    T TLeM4

    Thanks. This is the commands results:

    $ cat /etc/netplan/50-cloud-init.yaml
    network:
        version: 2
        renderer: networkd
        ethernets:
            eth0:
                addresses:
                - 45.83.105.92/22
                - 2a03:4000:46:463:880b:33ff:fe29:8d7c/64
                gateway4: 45.83.104.1
                gateway6: fe80::1
                match:
                    macaddress: 8a:0b:33:29:8d:7c
    
    $ cat /etc/resolv.conf
    # This is /run/systemd/resolve/stub-resolv.conf managed by man:systemd-resolved(8).
    # Do not edit.
    #
    # This file might be symlinked as /etc/resolv.conf. If you're looking at
    # /etc/resolv.conf and seeing this text, you have followed the symlink.
    #
    # This is a dynamic resolv.conf file for connecting local clients to the
    # internal DNS stub resolver of systemd-resolved. This file lists all
    # configured search domains.
    #
    # Run "resolvectl status" to see details about the uplink DNS servers
    # currently in use.
    #
    # Third party programs should typically not access this file directly, but only
    # through the symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a
    # different way, replace this symlink by a static file or a different symlink.
    #
    # See man:systemd-resolved.service(8) for details about the supported modes of
    # operation for /etc/resolv.conf.
    
    nameserver 127.0.0.53
    options edns0 trust-ad
    search .
    
    $ systemctl status systemd-resolved
    ● systemd-resolved.service - Network Name Resolution
         Loaded: loaded (/lib/systemd/system/systemd-resolved.service; enabled; vendor preset: enabled)
         Active: active (running) since Sat 2024-08-10 09:56:51 UTC; 3 days ago
           Docs: man:systemd-resolved.service(8)
                 man:org.freedesktop.resolve1(5)
                 https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers
                 https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients
       Main PID: 14835 (systemd-resolve)
         Status: "Processing requests..."
          Tasks: 1 (limit: 19050)
         Memory: 4.9M
            CPU: 1min 33.372s
         CGroup: /system.slice/systemd-resolved.service
                 └─14835 /lib/systemd/systemd-resolved
    
    Notice: journal has been rotated since unit was started, output may be incomplete.
    
    Support update dns

  • Auto-Update to 8.0.3 - systemd-resolved empty response
    T TLeM4

    @girish this is a public VPS (this one)
    This is the command result:

    resolvectl |cat
    Global
           Protocols: -LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
    resolv.conf mode: stub
    
    Link 2 (eth0)
    Current Scopes: none
         Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
    
    Link 3 (docker0)
    Current Scopes: none
         Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
    
    Link 4 (br-3d41c8b84b0d)
    Current Scopes: none
         Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
    
    Link 6 (veth80c01b5)
    Current Scopes: none
         Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
    
    Link 8 (vethe16e1d4)
    Current Scopes: none
         Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
    
    Link 10 (vethed7b139)
    Current Scopes: none
         Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
    
    Link 12 (vethe67b486)
    Current Scopes: none
         Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
    
    Link 14 (vethd4ef98c)
    Current Scopes: none
         Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
    
    Link 16 (vethe6749b8)
    Current Scopes: none
         Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
    
    Link 20 (veth9b5beb5)
    Current Scopes: none
         Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
    
    Link 22 (vethe3dfaa9)
    Current Scopes: none
         Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
    
    Link 24 (veth109052f)
    Current Scopes: none
         Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
    
    Link 26 (veth093bad2)
    Current Scopes: none
         Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
    
    Link 28 (vethe6fe0f0)
    Current Scopes: none
         Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
    
    Link 30 (veth4c250c4)
    Current Scopes: none
         Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
    
    Link 32 (veth9612c7c)
    Current Scopes: none
         Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
    
    Link 34 (veth32f80d0)
    Current Scopes: none
         Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
    
    Link 38 (veth362eae4)
    Current Scopes: none
         Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
    
    Link 42 (veth4c8efe9)
    Current Scopes: none
         Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
    
    Link 44 (veth75c6814)
    Current Scopes: none
         Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
    
    Link 46 (vethf18555a)
    Current Scopes: none
         Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
    
    Link 48 (vetha0fbec1)
    Current Scopes: none
         Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
    
    Link 52 (vethd427026)
    Current Scopes: none
         Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
    
    Link 54 (veth2b70d82)
    Current Scopes: none
         Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
    
    Link 56 (vetha7b4ccb)
    Current Scopes: none
         Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
    
    Link 58 (veth1894ed4)
    Current Scopes: none
         Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
    
    Link 60 (vetheadf5c5)
    Current Scopes: none
         Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
    
    Link 62 (veth69ed68b)
    Current Scopes: none
         Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
    
    Link 64 (veth6b6f42a)
    Current Scopes: none
         Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
    
    Link 66 (vethc2e2a32)
    Current Scopes: none
         Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
    
    Link 70 (vetha39cf1d)
    Current Scopes: none
         Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
    
    Link 72 (veth3493a4d)
    Current Scopes: none
         Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
    
    Link 74 (veth79e2f75)
    Current Scopes: none
         Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
    
    Link 76 (vethc6fa10b)
    Current Scopes: none
         Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
    
    Link 98 (veth40adda1)
    Current Scopes: none
         Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
    
    Link 104 (vethb251de5)
    Current Scopes: none
         Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
    
    Link 128 (veth2a70946)
    Current Scopes: none
         Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
    
    Link 130 (vethc338380)
    Current Scopes: none
         Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
    
    Link 132 (veth34771c4)
    Current Scopes: none
         Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
    
    Link 134 (vethd1f944b)
    Current Scopes: none
         Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
    
    Support update dns

  • Auto-Update to 8.0.3 - systemd-resolved empty response
    T TLeM4

    Hi,

    An automatic upgrade happened this night on our server and all DNS queries result in empty response from systemd-resolved.

    Here a part of the box.log where we saw the first error:

    2024-08-10T01:33:35.165Z box:apphealthmonitor app health: 24 running / 2 stopped / 0 unresponsive
    2024-08-10T01:33:36.851Z box:box Received SIGTERM. Shutting down.
    2024-08-10T01:33:36.858Z box:platform uninitializing platform
    2024-08-10T01:33:36.859Z box:shell startTask: /usr/bin/sudo -S -E /home/yellowtent/box/src/scripts/starttask.sh 12905 /home/yellowtent/platformdata/logs/tasks/12905.log 15 1024 errored BoxError: startTask exited with code null signal SIGTERM
        at ChildProcess.<anonymous> (/home/yellowtent/box/src/shell.js:110:19)
        at ChildProcess.emit (node:events:513:28)
        at ChildProcess._handle.onexit (node:internal/child_process:291:12) {
      reason: 'Shell Error',
      details: {},
      code: null,
      signal: 'SIGTERM'
    }
    2024-08-10T01:33:36.934Z box:tasks startTask: 12905 completed with code null
    2024-08-10T01:33:36.937Z box:tasks setCompleted - 12905: {"error":{"message":"Task 12905 crashed with code null","code":"crashed"}}
    2024-08-10T01:33:36.937Z box:tasks update 12905: {"percent":100,"error":{"message":"Task 12905 crashed with code null","code":"crashed"}}
    2024-08-10T01:33:36.938Z box:platform onDeactivated: stopping post activation services
    2024-08-10T01:33:36.939Z box:tasks stopAllTasks: stopping all tasks
    2024-08-10T01:33:36.940Z box:shell stopTask /usr/bin/sudo -S /home/yellowtent/box/src/scripts/stoptask.sh all
    2024-08-10T01:33:36.952Z box:locker Released : box_update
    2024-08-10T01:33:36.952Z box:updater Update failed with error. { message: 'Task 12905 crashed with code null', code: 'crashed' }
    2024-08-10T01:33:36.953Z box:tasks startTask: 12905 done. error: { message: 'Task 12905 crashed with code null', code: 'crashed' }
    2024-08-10T01:35:10.561Z box:server ==========================================
    2024-08-10T01:35:10.562Z box:server            Cloudron 8.0.3  
    2024-08-10T01:35:10.562Z box:server ==========================================
    2024-08-10T01:35:10.562Z box:platform initialize: start platform
    2024-08-10T01:35:10.902Z box:tasks stopAllTasks: stopping all tasks
    2024-08-10T01:35:10.902Z box:shell stopTask /usr/bin/sudo -S /home/yellowtent/box/src/scripts/stoptask.sh all
    sudo: unable to resolve host my: Temporary failure in name resolution
    All tasks stopped
    2024-08-10T01:35:11.141Z box:reverseproxy writeDashboardConfig: writing dashboard config for a38.fr
    2024-08-10T01:35:11.158Z box:shell isOscpEnabled execArgs: openssl ["x509","-in","/home/yellowtent/platformdata/nginx/cert/_.a38.fr.cert","-noout","-ocsp_uri"]
    2024-08-10T01:35:11.179Z box:shell reload /usr/bin/sudo -S /home/yellowtent/box/src/scripts/restartservice.sh nginx
    sudo: unable to resolve host my: Temporary failure in name resolution
    nginx: [warn] "ssl_stapling" ignored, host not found in OCSP responder "e5.o.lencr.org" in the certificate "/home/yellowtent/platformdata/nginx/cert/_.a38.fr.cert"
    nginx: [warn] "ssl_stapling" ignored, host not found in OCSP responder "e5.o.lencr.org" in the certificate "/home/yellowtent/platformdata/nginx/cert/a38.fr.cert"
    nginx: [warn] "ssl_stapling" ignored, host not found in OCSP responder "e5.o.lencr.org" in the certificate "/home/yellowtent/platformdata/nginx/cert/_.a38.fr.cert"
    nginx: [warn] "ssl_stapling" ignored, host not found in OCSP responder "e5.o.lencr.org" in the certificate "/home/yellowtent/platformdata/nginx/cert/_.a38.fr.cert"
    

    dig response:

    $ dig api.cloudron.io
    
    ; <<>> DiG 9.18.28-0ubuntu0.22.04.1-Ubuntu <<>> api.cloudron.io
    ;; global options: +cmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 12668
    ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
    
    ;; OPT PSEUDOSECTION:
    ; EDNS: version: 0, flags:; udp: 65494
    ;; QUESTION SECTION:
    ;api.cloudron.io.		IN	A
    
    ;; Query time: 0 msec
    ;; SERVER: 127.0.0.53#53(127.0.0.53) (UDP)
    ;; WHEN: Sat Aug 10 15:56:07 UTC 2024
    ;; MSG SIZE  rcvd: 44
    

    All apps were in error state and i successfully started them all with write api.cloudron.io in host file and retry configure task in cloudron panel.

    Unfortunately, this is only temporary fix as dns issue is still there and app store for example is still unavailable (so i commented out this fix).

    Support update dns

  • Forge app update
    T TLeM4

    I think i have some crash with the new release.
    Update from 1.16.5.

    I have the full log if you need it

    2022-05-08T01:22:51.000Z at processTimers (internal/timers.js:497:7) [ /app/code/node_modules/express/lib/application.js:630:43 ]
    2022-05-08T01:22:51.000Z ERROR ServiceUnavailableError: Response timeout
    2022-05-08T01:22:51.000Z at IncomingMessage.<anonymous> (/app/code/node_modules/connect-timeout/index.js:84:8)
    2022-05-08T01:22:51.000Z at IncomingMessage.emit (events.js:315:20)
    2022-05-08T01:22:51.000Z at Timeout.<anonymous> (/app/code/node_modules/connect-timeout/index.js:49:11)
    2022-05-08T01:22:51.000Z at listOnTimeout (internal/timers.js:554:17)
    2022-05-08T01:22:51.000Z at processTimers (internal/timers.js:497:7) [ /app/code/node_modules/express/lib/application.js:630:43 ]
    2022-05-08T01:24:38.000Z ERROR LDAP error connect ETIMEDOUT 172.18.0.1:3002 [ /app/code/backend/routes.js:75:21 ]
    2022-05-08T01:24:38.000Z connect ETIMEDOUT 172.18.0.1:3002 Error: connect ETIMEDOUT 172.18.0.1:3002
    2022-05-08T01:24:38.000Z at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1146:16)
    2022-05-08T01:24:50.000Z ERROR LDAP error connect ETIMEDOUT 172.18.0.1:3002 [ /app/code/backend/routes.js:75:21 ]
    2022-05-08T01:24:50.000Z connect ETIMEDOUT 172.18.0.1:3002 Error: connect ETIMEDOUT 172.18.0.1:3002
    2022-05-08T01:24:50.000Z at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1146:16)
    2022-05-08T01:24:50.000Z ERROR LDAP error connect ETIMEDOUT 172.18.0.1:3002 [ /app/code/backend/routes.js:75:21 ]
    2022-05-08T01:24:50.000Z connect ETIMEDOUT 172.18.0.1:3002 Error: connect ETIMEDOUT 172.18.0.1:3002
    2022-05-08T01:24:50.000Z at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1146:16)
    2022-05-08T18:25:11.000Z [18:25:11] [Server thread/INFO] [ne.mi.co.AdvancementLoadFix/]: Using new advancement loading for net.minecraft.advancements.PlayerAdvancements@6122d325
    2022-05-08T18:25:11.000Z [18:25:11] [Server thread/INFO] [minecraft/PlayerList]: User3[/3.4.5.6:56382] logged in with entity id 139 at (20.849399336919795, 73.0, -53.43918182426666)
    2022-05-08T18:25:11.000Z [18:25:11] [Server thread/INFO] [minecraft/DedicatedServer]: User3 joined the game
    2022-05-08T18:30:05.000Z [18:30:05] [Server thread/INFO] [minecraft/DedicatedServer]: User3 has made the advancement [Sweet Dreams]
    2022-05-08T20:23:40.000Z [20:23:40] [Server thread/INFO] [minecraft/ServerPlayNetHandler]: User3 lost connection: Disconnected
    2022-05-08T20:23:40.000Z [20:23:40] [Server thread/INFO] [minecraft/DedicatedServer]: User3 left the game
    2022-05-09T08:38:56.000Z => Ensure directories
    2022-05-09T08:38:56.000Z => Accept EULA
    2022-05-09T08:38:56.000Z => Update server port
    2022-05-09T08:38:56.000Z => Update query port
    2022-05-09T08:38:56.000Z => Disable rcon port
    2022-05-09T08:38:56.000Z => Ensure permissions
    2022-05-09T08:38:56.000Z => Starting management server
    2022-05-09T08:38:56.000Z Use ldap auth
    2022-05-09T08:38:56.000Z Server is up and running on port 3000
    2022-05-09T08:38:56.000Z start minecraft server with memory limit 1638 M
    2022-05-09T08:38:56.000Z Error: could not open `libraries/net/minecraftforge/forge/1.18.2-40.1.0/unix_args.txt'
    2022-05-09T08:39:39.000Z => Ensure directories
    2022-05-09T08:39:39.000Z => Accept EULA
    2022-05-09T08:39:39.000Z => Update server port
    2022-05-09T08:39:39.000Z => Update query port
    2022-05-09T08:39:39.000Z => Disable rcon port
    2022-05-09T08:39:39.000Z => Ensure permissions
    2022-05-09T08:39:39.000Z => Starting management server
    2022-05-09T08:39:40.000Z Use ldap auth
    2022-05-09T08:39:41.000Z Server is up and running on port 3000
    2022-05-09T08:39:41.000Z start minecraft server with memory limit 1638 M
    2022-05-09T08:39:41.000Z Error: could not open `libraries/net/minecraftforge/forge/1.18.2-40.1.0/unix_args.txt'
    
    Minecraft

  • Minecraft admin UI LDAP errors
    T TLeM4

    Hi everyone, same issue happen here.

    Application reboot temporarily fix the issue, but it always come back.

    Is there any workaround other than app reboot, as this solution disconnect players and i need to connect myself to the game only to know/tell that i will reboot only for that...

    I 'm open to any workaround or quick fix that allow to use the minecraft server console while the admin panel (LDAP it seems) crashed or allow to reboot the admin panel without rebooting the game.
    At least a solution to see the game log without connecting to the game ?

    Currently it seems the that it's the admin panel that start the game so i think it's needed to change the code.

    Thank you all !

    Minecraft
  • Login

  • Don't have an account? Register

  • Login or register to search.
  • First post
    Last post
0
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search