-
Notifications
You must be signed in to change notification settings - Fork 61
Description
Hi there, I have my Monograph up at https://monograph.revsuine.xyz/ which is up and running, e.g. if you go to that link you can see the Monograph homepage.
When I publish monographs, my client (3.3.7-c560685-desktop) gives a url, e.g.
However, opening this url gives a 404:
I have tried to publish multiple notes and am experiencing the same thing for all notes I try to publish.
I've tried with the provided docker compose in the repo, as well as with the suggested changes in #75 and #78; in both cases, the behaviour is the same. Tracking latest for all the Notesnook containers so beta.8 for Monograph and the other containers.
No new logs seem to appear when I try to publish a note (I tested by watching the logs before and after trying to publish). However, the logs do show a bunch of errors. I'm attaching logs to the issue; they are very long, although attaching them all for completeness. Relevant errors I think might be these?
error: No route matches URL "/monographs/.gitconfig"
at getInternalRouterError (/home/bun/app/node_modules/@remix-run/router/dist/router.cjs.js:5229:59)
at query (/home/bun/app/node_modules/@remix-run/router/dist/router.cjs.js:3808:19)
at query (/home/bun/app/node_modules/@remix-run/router/dist/router.cjs.js:3773:24)
at handleDocumentRequest (/home/bun/app/node_modules/@remix-run/server-runtime/dist/server.js:313:35)
at handleDocumentRequest (/home/bun/app/node_modules/@remix-run/server-runtime/dist/server.js:310:38)
at requestHandler (/home/bun/app/node_modules/@remix-run/server-runtime/dist/server.js:170:24)
at requestHandler (/home/bun/app/node_modules/@remix-run/server-runtime/dist/server.js:74:40)
ErrorResponseImpl {
status: 404,
statusText: "Not Found",
internal: true,
data: "Error: No route matches URL \"/monographs/.gitconfig\"",
error: 5224 | errorMessage = "You made a " + method.toUpperCase() + " request to \"" + pathname + "\" but " + ("did not provide an `action` for route \"" + routeId + "\", ") + "so there is no way to handle the request.";
5225 | } else if (method) {
5226 | errorMessage = "Invalid request method \"" + method.toUpperCase() + "\"";
5227 | }
5228 | }
5229 | return new ErrorResponseImpl(status || 500, statusText, new Error(errorMessage), true);
^
error: No route matches URL "/monographs/.gitconfig"
at getInternalRouterError (/home/bun/app/node_modules/@remix-run/router/dist/router.cjs.js:5229:59)
at query (/home/bun/app/node_modules/@remix-run/router/dist/router.cjs.js:3808:19)
at query (/home/bun/app/node_modules/@remix-run/router/dist/router.cjs.js:3773:24)
at handleDocumentRequest (/home/bun/app/node_modules/@remix-run/server-runtime/dist/server.js:313:35)
at handleDocumentRequest (/home/bun/app/node_modules/@remix-run/server-runtime/dist/server.js:310:38)
at requestHandler (/home/bun/app/node_modules/@remix-run/server-runtime/dist/server.js:170:24)
at requestHandler (/home/bun/app/node_modules/@remix-run/server-runtime/dist/server.js:74:40)
,
}
ErrorResponseImpl {
status: 404,
statusText: "Not Found",
internal: true,
data: "Error: No route matches URL \"/monographs/.gitconfig\"",
error: 5224 | errorMessage = "You made a " + method.toUpperCase() + " request to \"" + pathname + "\" but " + ("did not provide an `action` for route \"" + routeId + "\", ") + "so there is no way to handle the request.";
5225 | } else if (method) {
5226 | errorMessage = "Invalid request method \"" + method.toUpperCase() + "\"";
5227 | }
5228 | }
5229 | return new ErrorResponseImpl(status || 500, statusText, new Error(errorMessage), true);
error: No route matches URL "/monographs/.env.deploy"
at getInternalRouterError (/home/bun/app/node_modules/@remix-run/router/dist/router.cjs.js:5229:59)
at query (/home/bun/app/node_modules/@remix-run/router/dist/router.cjs.js:3808:19)
at query (/home/bun/app/node_modules/@remix-run/router/dist/router.cjs.js:3773:24)
at handleDocumentRequest (/home/bun/app/node_modules/@remix-run/server-runtime/dist/server.js:313:35)
at handleDocumentRequest (/home/bun/app/node_modules/@remix-run/server-runtime/dist/server.js:310:38)
at requestHandler (/home/bun/app/node_modules/@remix-run/server-runtime/dist/server.js:170:24)
at requestHandler (/home/bun/app/node_modules/@remix-run/server-runtime/dist/server.js:74:40)
,
}
ErrorResponseImpl {
status: 404,
statusText: "Not Found",
internal: true,
data: "Error: No route matches URL \"/monographs/.env.deploy\"",
error: 5224 | errorMessage = "You made a " + method.toUpperCase() + " request to \"" + pathname + "\" but " + ("did not provide an `action` for route \"" + routeId + "\", ") + "so there is no way to handle the request.";
5225 | } else if (method) {
5226 | errorMessage = "Invalid request method \"" + method.toUpperCase() + "\"";
5227 | }
5228 | }
5229 | return new ErrorResponseImpl(status || 500, statusText, new Error(errorMessage), true);
^
error: No route matches URL "/monographs/.env.deploy"
at getInternalRouterError (/home/bun/app/node_modules/@remix-run/router/dist/router.cjs.js:5229:59)
at query (/home/bun/app/node_modules/@remix-run/router/dist/router.cjs.js:3808:19)
at query (/home/bun/app/node_modules/@remix-run/router/dist/router.cjs.js:3773:24)
at handleDocumentRequest (/home/bun/app/node_modules/@remix-run/server-runtime/dist/server.js:313:35)
at handleDocumentRequest (/home/bun/app/node_modules/@remix-run/server-runtime/dist/server.js:310:38)
at requestHandler (/home/bun/app/node_modules/@remix-run/server-runtime/dist/server.js:170:24)
at requestHandler (/home/bun/app/node_modules/@remix-run/server-runtime/dist/server.js:74:40)
,
}
Edit: I think the quoted requests in the log might be from web scrapers not from me trying the url given by the client. The URL from the client does give a 404: https://monograph.revsuine.xyz/69616c4ecca15baba5b496f1
It seems like visiting the URLs the client gives me doesn't leave logs. I'm wondering if it might be an issue with my reverse proxy config—I've not touched it since this stopped working (I published notes with Monograph a few months ago which worked; it's only recently I've had this issue) but I'm thinking maybe nginx is not forwarding requests correctly. I will check this tomorrow.