It sounds like the update may have changed how aaPanel handles proxy rules or internal networking. A 502 usually indicates that Nginx is unable to connect to your container on the expected port. A couple of things you could try checking:
- Ensure the container is still running and bound to 127.0.0.1:3035 after the update (note that Docker's defaults may change).
- Confirm that your proxy configuration in aaPanel hasn’t been reset or overwritten during the upgrade — I’ve seen updates clear custom rules.
- Also worth testing is whether the service is reachable directly on the port without Nginx, just to rule out whether the issue lies with the app itself or only the proxy.
I’ve had a similar issue after a panel upgrade, where I just needed to reapply the proxy settings, and it worked again.
