-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
The module at "/pad" does not exist. nginx, reverse proxy #515
Comments
Should be fixed by af4bd5c, could you check? |
Also, thanks for the good error report. |
No. not really. Still the same error. |
Confirmed. This is fixed. Thanks for the great support and all the work! :-) |
With this merged into current master I still get the same error. :-( |
@mmehnert, possibly, but at least some HTTP data. Requests are made to nginx, requests made to the etherpad instance (from nginx), and their responses will help diagnose this issue. It must be something with redirects, but, without more data, I couldn’t say exactly what. |
Do you prefer Vmware or Virtualbox? |
Found something. It works fine in standard configuration. The Problem appears as soon as I set httpAuth in settings.json. That somehow messes up everything.
|
Ah, ok, then the fix should be pretty straight forward, I don’t see any reason for static assets to require authentication. Master is in limbo right now, but just move the block at server.js:127 beneath the static assets and that should fix it.. |
Hmm. I moved it to line 152 but somehow I could see content of pads without entering the password then. (restarted the browser but login was not requested.) |
the same error occurs to me and I had no http auth activated. But I used the specific IP of the etherpad host in my network and not the loopback. So with 0.0.0.0 everything works fine to me. |
same here as jubro explains. Just in case: Debian Wheezy |
status? |
still the same in
|
I mean, its possible to use nginx for authentication - then it's all fine. But the etherpad-lite authentication does not work through nginx. |
But it appears to work in the current development branch. 916e52a |
nginx is configured as described in the wiki.
stacktrace with commit
599c8c7
_designatedRequire()require-kernel.js (line 569)
path = "/pad"
continuation = undefined
designatedRequire()require-kernel.js (line 589)
path = "/pad"
continuation = undefined
requireRelative()require-kernel.js (line 595)
basePath = "/"
qualifiedPath = "/pad"
continuation = undefined
require()require-kernel.js (line 630)
qualifiedPath = "/pad"
continuation = undefined
(?)()RCtKLMMYOg (line 301)
RCtKLMMYOg()RCtKLMMYOg (line 298)
which comes from "require('/pad').init();" in the static pad.html
bisected:
dcc0740 is the first bad commit
commit dcc0740
Author: Chad Weider cweider@oofn.net
Date: Sun Jan 29 03:30:31 2012 -0800
:040000 040000 d97ce18d9fd67fadde681cf32b8ac29a5015acb0 88ad5af498b47d3f7b0fe5496ade364f6abf6e4d M node
:100644 100644 27b2125a1229e20422302b59732e3bba60f5fb7b e92905b7c1ab2d6cf0bab10e5ca46d8d15d029a9 M package.json
:040000 040000 3984e172e0ac28f57c52ebb6104eb4a1f6c12fc5 3dc99ec4c3bf07e1272e2e4480bafdba7714358d M static
The text was updated successfully, but these errors were encountered: