#3354: 504 Gateway Time-out | video.osgeo.org
-------------------------------+-----------------------
Reporter: strk | Owner: robe
Type: task | Status: new
Priority: major | Milestone: Unplanned
Component: SysAdmin/Peertube | Keywords:
-------------------------------+-----------------------
I was able to see a couple videos today, pasted their URLs to OSGeo
General Matrix room, logged in the peervideo instance and started getting
504 Gateway Time-out all over.
Example, from here:
https://video.osgeo.org/w/wW6C35eMtjUz2rpfiW4ENc
I was trying to improve discoverability of videos by adding some tags
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/3354>
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.
#3354: 504 Gateway Time-out | video.osgeo.org
-------------------------------+------------------------
Reporter: strk | Owner: robe
Type: task | Status: closed
Priority: major | Milestone: Unplanned
Component: SysAdmin/Peertube | Resolution: fixed
Keywords: |
-------------------------------+------------------------
Changes (by robe):
* resolution: => fixed
* status: new => closed
Comment:
Okay this is annoying. video.osgeo.org the nginx service shutdown because
it couldn't reach nginx.lxd.
When I restarted peertube container nginx did not come back. I guess
maybe because the dns resolver or something started after nginx did, so
local nginx gave up when it couldn't resolve nginx.lxd ip. I guess I
could hard-code that, but then that would cause oteher issues if the
nginx.lxd ip changes and we still might have an issue if nginx comes up
after the containers.
Anyway video.osgeo.org is back up now.
I'm going to close this for now. Feel free to reopen if it happens again.
--
Ticket URL: <#3354 (504 Gateway Time-out | video.osgeo.org) – OSGeo;
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.
#3354: 504 Gateway Time-out | video.osgeo.org
-------------------------------+------------------------
Reporter: strk | Owner: robe
Type: task | Status: closed
Priority: major | Milestone: Unplanned
Component: SysAdmin/Peertube | Resolution: fixed
Keywords: |
-------------------------------+------------------------
Comment (by strk):
I think it would help to use static IPs for those containers. After all we
know which containers we have, why not using static ? They could be
encoded in Ansible too
--
Ticket URL: <#3354 (504 Gateway Time-out | video.osgeo.org) – OSGeo;
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.