Skip to content

Unable to access Replayweb.Page externally #2

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
brisnick opened this issue Feb 26, 2025 · 1 comment
Open

Unable to access Replayweb.Page externally #2

brisnick opened this issue Feb 26, 2025 · 1 comment

Comments

@brisnick
Copy link

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.

@wvengen
Copy link
Member

wvengen commented Feb 28, 2025

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).

Could this be something related to CORS?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants