I was turning on IPV6 in my router settings, and in order to do so, my router had to reboot, and without thinking, I went ahead. I then realised, my server is connected to said router, so after the router rebooted, I checked and saw that most of the docker containers were fine, except for the Piped container.

When I go to the Piped instance that’s hosted on my domain, it just brings up a Cloudflare Code 522 Error (I use Cloudflare)I tried restarting the containers over and over again but no luck. Any advice? I will provide more information if needed.

EDIT: It’s now solved. Apparently during the router reboot my ISP changed my IPv4 address.

  • asudox@discuss.tchncs.deEnglish
    1·
    9 days ago

    It seems like the 522 CF error happens when the connection times out (the server did not respond within x seconds). Can you provide the logs for the Piped container?

    • amogussussywussy@sh.itjust.worksOPEnglish
      2·
      9 days ago

      Sure, here they are. INFO: Command execution complete ThrottlingCache: 0 entries SLF4J: No SLF4J providers were found. SLF4J: Defaulting to no-operation (NOP) logger implementation SLF4J: See https://www.slf4j.org/codes.html#noProviders for further details. Dec 20, 2024 5:07:46 AM org.hibernate.Version logVersion INFO: HHH000412: Hibernate ORM core version [WORKING] Dec 20, 2024 5:07:47 AM org.hibernate.cache.internal.RegionFactoryInitiator initiateService INFO: HHH000026: Second-level cache disabled Dec 20, 2024 5:07:47 AM org.hibernate.engine.jdbc.connections.internal.ConnectionProviderInitiator initiateService INFO: HHH000130: Instantiating explicit connection provider: org.hibernate.hikaricp.internal.HikariCPConnectionProvider Dec 20, 2024 5:07:47 AM org.hibernate.engine.jdbc.dialect.internal.DialectFactoryImpl constructDialect WARN: HHH90000025: PostgreSQLDialect does not need to be specified explicitly using 'hibernate.dialect' (remove the property setting and it will be selected by default) Logged in as user: null Room ID: !CfXSiQMnWTEPfnBNuK:matrix.org Filter ID: null Dec 20, 2024 5:07:49 AM org.hibernate.engine.transaction.jta.platform.internal.JtaPlatformInitiator initiateService INFO: HHH000489: No JTA platform available (set 'hibernate.transaction.jta.platform' to enable JTA platform integration) Database connection is ready! PubSub: queue size - 0 channels Cleanup: Removed 0 old videos ThrottlingCache: 0 entries Cleanup: Removed 0 old videos PubSub: queue size - 0 channels

      • asudox@discuss.tchncs.deEnglish
        1·
        9 days ago

        I don’t see anything wrong in the logs. Must be something else.

        Can you reach the piped container through localhost? Did you try to access it without the cloudflare proxy (it can be disabled in the cloudflare dns settings)?

        Also check what the other guy said, it also could be that.

        • amogussussywussy@sh.itjust.worksOPEnglish
          2·
          9 days ago

          I just realised that I also cannot access my main website, so that leads me to conclude that it might be my reverse proxy, Nginx Proxy Manager.

          I dunno, so please take a look at the logs for Nginx Proxy Manager. [12/20/2024] [7:17:41 AM] [Nginx ] › ℹ info Reloading Nginx [12/20/2024] [7:17:41 AM] [Global ] › ⬤ debug CMD: /usr/sbin/nginx -s reload [12/20/2024] [7:17:45 AM] [Nginx ] › ⬤ debug Deleting file: /data/nginx/proxy_host/5.conf [12/20/2024] [7:17:45 AM] [Global ] › ⬤ debug CMD: /usr/sbin/nginx -t -g "error_log off;" [12/20/2024] [7:17:45 AM] [Nginx ] › ℹ info Reloading Nginx [12/20/2024] [7:17:45 AM] [Global ] › ⬤ debug CMD: /usr/sbin/nginx -s reload [12/20/2024] [7:17:46 AM] [Global ] › ⬤ debug CMD: /usr/sbin/nginx -t -g "error_log off;" [12/20/2024] [7:17:46 AM] [Nginx ] › ⬤ debug Deleting file: /data/nginx/proxy_host/5.conf [12/20/2024] [7:17:46 AM] [Nginx ] › ⬤ debug Could not delete file: { "errno": -2, "code": "ENOENT", "syscall": "unlink", "path": "/data/nginx/proxy_host/5.conf" } [12/20/2024] [7:17:46 AM] [Global ] › ⬤ debug CMD: /usr/sbin/nginx -t -g "error_log off;" [12/20/2024] [7:17:46 AM] [Global ] › ⬤ debug CMD: /usr/sbin/nginx -t -g "error_log off;" [12/20/2024] [7:17:46 AM] [Nginx ] › ℹ info Reloading Nginx [12/20/2024] [7:17:46 AM] [Global ] › ⬤ debug CMD: /usr/sbin/nginx -s reload [12/20/2024] [7:17:47 AM] [Nginx ] › ⬤ debug Deleting file: /data/nginx/proxy_host/3.conf [12/20/2024] [7:17:47 AM] [Global ] › ⬤ debug CMD: /usr/sbin/nginx -t -g "error_log off;" [12/20/2024] [7:17:47 AM] [Nginx ] › ℹ info Reloading Nginx [12/20/2024] [7:17:47 AM] [Global ] › ⬤ debug CMD: /usr/sbin/nginx -s reload [12/20/2024] [7:17:49 AM] [Global ] › ⬤ debug CMD: /usr/sbin/nginx -t -g "error_log off;" [12/20/2024] [7:17:49 AM] [Nginx ] › ⬤ debug Deleting file: /data/nginx/proxy_host/3.conf [12/20/2024] [7:17:49 AM] [Nginx ] › ⬤ debug Could not delete file: { "errno": -2, "code": "ENOENT", "syscall": "unlink", "path": "/data/nginx/proxy_host/3.conf" } [12/20/2024] [7:17:49 AM] [Global ] › ⬤ debug CMD: /usr/sbin/nginx -t -g "error_log off;" [12/20/2024] [7:17:49 AM] [Global ] › ⬤ debug CMD: /usr/sbin/nginx -t -g "error_log off;" [12/20/2024] [7:17:49 AM] [Nginx ] › ℹ info Reloading Nginx [12/20/2024] [7:17:49 AM] [Global ] › ⬤ debug CMD: /usr/sbin/nginx -s reload [12/20/2024] [7:17:54 AM] [Nginx ] › ⬤ debug Deleting file: /data/nginx/proxy_host/4.conf [12/20/2024] [7:17:54 AM] [Global ] › ⬤ debug CMD: /usr/sbin/nginx -t -g "error_log off;" [12/20/2024] [7:17:54 AM] [Nginx ] › ℹ info Reloading Nginx [12/20/2024] [7:17:54 AM] [Global ] › ⬤ debug CMD: /usr/sbin/nginx -s reload [12/20/2024] [7:17:55 AM] [Global ] › ⬤ debug CMD: /usr/sbin/nginx -t -g "error_log off;" [12/20/2024] [7:17:55 AM] [Nginx ] › ⬤ debug Deleting file: /data/nginx/proxy_host/4.conf [12/20/2024] [7:17:55 AM] [Nginx ] › ⬤ debug Could not delete file: { "errno": -2, "code": "ENOENT", "syscall": "unlink", "path": "/data/nginx/proxy_host/4.conf"

          • asudox@discuss.tchncs.deEnglish
            1·
            9 days ago

            I haven’t really used Nginx, but from a quick look nginx seems to be restarting everytime as it attempts to delete some proxy configuration (?), but fails to do so with code “ENOENT” which just means that such file or directory does not exist.

            I also found this issue in the nginx github repo: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3497

            According to the discussion in that issue, it seems like nginx is the one causing the problems. Consider downgrading the nginx container image to what it was before if it updated itself.

            It also could be something being corrupted, so you might need to dig some more into this matter.

            People also recommend switching to other reverse proxies like caddy and traefik. I also recommend it, you might as well take this as a opportunity to use something better. I personally recommend Caddy, as it is very simple to configure and very convenient. It handles HTTPS and all that boring stuff for you. Iirc it also has a cloudflare module, so you can just follow the guide in the documentations to let Caddy automatically renew certs for you via access tokens.