You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a host server which is using NGinx to reverse-proxying /replay to the Replayweb.page docker install.
On load of the page from the host server, everything works as expected.
When loading the page from a device on the same network to the host server the Replayweb.page opens, but I get a non-stop list of 404 errors for coll-index. Needless to say the WARC file cannot be loaded and therefore viewed.
Is there a way around this so the Docker container version of Replayweb.page can be exposed to other devices on a private network.
The text was updated successfully, but these errors were encountered:
I'm trying to wrap my head around your use-case.
Replayweb.page is a client-side application, it loads assets from the server, and then does the WARC/WACZ loading fully client-side. So if you have problems accessing a WARC file, this is related to the server serving the WARC file, and/or how Replayweb.page accesses it. I don't really see how the Docker packaging comes into play here (though I may be missing something).
I have a host server which is using NGinx to reverse-proxying /replay to the Replayweb.page docker install.
On load of the page from the host server, everything works as expected.
When loading the page from a device on the same network to the host server the Replayweb.page opens, but I get a non-stop list of 404 errors for coll-index. Needless to say the WARC file cannot be loaded and therefore viewed.
Is there a way around this so the Docker container version of Replayweb.page can be exposed to other devices on a private network.
The text was updated successfully, but these errors were encountered: