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
// set to serve PsiTransfer from a sub-path
"baseUrl": '/securedownload',
// use to set custom upload url (subfolder to baseUrl)
"uploadAppPath": '/upload/',
The error page pops up, saying that a download bucket was not found. Notably this showed that there's a duplication of the baseUrl into the upload URL;
I've found that this line in config.js appears to be causing this duplication; config.uploadAppPath = config.baseUrl.substr(0, config.baseUrl.length - 1) + config.uploadAppPath;
and by commenting it out, I was able to use the URL /securedownload/upload/ without issue. This change was made in this commit
Other notes about my configuration;
I am using nginx reverse proxies to access an internal file server where psitransfer is running. It basically does a double proxy pass, from the main web server to the file server then to psitransfer;
webserver: proxy_pass "http://[fileserverip]:80;
fileserver: proxy_pass "http://127.0.0.1:3000";
So far I haven't found a reason why nginx would be the issue here, but I'm not 100% sure since I'm not an expert.
The text was updated successfully, but these errors were encountered:
When configuring these two variables as such;
The error page pops up, saying that a download bucket was not found. Notably this showed that there's a duplication of the baseUrl into the upload URL;
I've found that this line in config.js appears to be causing this duplication;
config.uploadAppPath = config.baseUrl.substr(0, config.baseUrl.length - 1) + config.uploadAppPath;
and by commenting it out, I was able to use the URL /securedownload/upload/ without issue. This change was made in this commit
Other notes about my configuration;
webserver:
proxy_pass "http://[fileserverip]:80;
fileserver:
proxy_pass "http://127.0.0.1:3000";
So far I haven't found a reason why nginx would be the issue here, but I'm not 100% sure since I'm not an expert.
The text was updated successfully, but these errors were encountered: