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
Copy file name to clipboardExpand all lines: README.md
+3Lines changed: 3 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -47,6 +47,8 @@ You must fill this out for the webserver to work properly. Below explains the co
47
47
"domain":"*.example.com", // Domain server will use. Will error if domain not used in request. Place "*" as the subdomain to enable wildcard subdomains for the webserver.
48
48
"puploadKeyGenLength":64, // Amount of characters server should use for pupload files
49
49
"public":false, // Disables auth and does not render a password field for /upload
50
+
"socket":"", // socket path to listen eg. /tmp/shares.sock
51
+
"socketOnly":true, // do not listen via ip if socket is set (ignore options secure, port)
50
52
"maxUploadSize":50, // max upload size for non-admins using regular key in MB
@@ -86,6 +88,7 @@ If you're configuring this webserver to run through an Nginx reverse proxy, make
86
88
proxy_set_header Upgrade $http_upgrade;
87
89
proxy_set_header Connection 'upgrade';
88
90
proxy_set_header Host $host;
91
+
proxy_set_header X-Forwarded-For $remote_addr;
89
92
proxy_cache_bypass $http_upgrade;
90
93
```
91
94
This is generally some things you want to add to your config, and is what's actually required for ShareS to work properly. This is because ShareS returns uploads like `[http/https]://[requested url]/[filename]` and since you're running ShareS through a reverse proxy, unless you're passing along the *original* headers, ShareS is most likely just going to send you something like `http://[server's real ip address]/[filename]`
0 commit comments