-
Notifications
You must be signed in to change notification settings - Fork 472
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
tusd on https #86
Comments
Intentionally, tusd serves its content only over HTTP and not HTTPS in order to reduce the project's complexity. This explains the |
Perhaps it's time to add a FAQ with |
Dear All, |
@kevin-openc Can you post the configuration of the reverse proxy here? |
sure, i am using apache instead of nginx, add lines in apache conf
the most important lines are below, to redirect https to http internally, so you can call https://localhost/files as endpoint
|
Thank you!
|
Thank you, @tameribrahim and @kevin-openc, for posting your configurations here. They will be very helpful for future users. I added a few sentences about this topic to the README (https://github.com/tus/tusd/blob/master/README.md#how-can-i-access-tusd-using-https), as @kvz suggested, so I hope it will be easier to get an answer to this question from now on. |
Hi all, To all, and especially to kevin-openc: As recommended by the docs, i am using tusd with the option -behind-proxy |
@johnypowaa Thank you for this information. I added an example configuration for Apache to the repository (https://github.com/tus/tusd/blob/master/.infra/files/apache2.conf) and added a link to it from the FAQ. |
Thank you, that's great. However, I don't know if this is valid for recent versions of Apache; My version of Apache is really old (2.2.9) |
I actually tested the configuration for myself today and it works, yet I added some comments to the file :) |
Dear All, Previously tusd was working well with https after disabling the mixed active content block, but now I cannot make it functional again. The demo page (https://192.168.111.101:8000/) works well with its endpoint (https://192.168.111.101:8000/files), but if I move the page into a https virtual host (https://192.168.111.101/tus/) with the same endpoint, I've also tried to use proxypass as described above, but the endpoint (https://192.168.111.101/files) gives the same error for both the demo and https pages. The endpoint itself should work, because using it in a browser gives
Do I miss something? 192.168.111.101 is a linux virtual machine. |
@krampampuli Are you sure you are using tusd? The output snippet you provided is generated by tusd, it has a bit different log format. To me it looks like you might be using tus-node-server instead. |
Right, sorry, I'm actually playing around with both. After some googling I've included the line
in my Apache config, and with this the https page works with the https endpoint. I guess it is needed because I have to use the IP address instead of Maybe you could include this line with a note in the example configuration. |
@krampampuli Thanks for the tip, I added it to the apache2 example 👍 |
Is there any working sample for .htaccess configuration? |
Do you intend to map an alias to it, i.e. |
alias, I guess. |
@djsg Setting up SSL only using .htaccess is apparently not possible: https://stackoverflow.com/a/38054124. I am not sure what your current configuration looks like, maybe you want to provide more details about that. |
I have a web app, which has a file upload page/function. I embed tus node client inside that page, and in the server I run tus node server. In my lab setting, I use Apache2 to redirect HTTPS traffic to my web server (80); and for a particular URL, it redirects to tus node sever (9001). The apache2.conf is almost same as (https://github.com/tus/tusd/blob/master/docs/apache2.conf), and it is working well. However, as I move my app to a web hosting site, I don't have the control of Apache2 setting. The only setting I can do is in .htaccess. So far for my web app in the hosting site, redirection from HTTP to HTTP is working. It is configured in .htaccess like What I need is redirection to local port 9001 if URL is like https://www.example.com/tus_upload |
Thanks for describing your problem in detail but I don't think I can help you there. Personally, I haven't used Apache2 enough to be able to answer your questions. Unless someone else can, I would recommend you to reach out to the Apache httpd community (https://httpd.apache.org/support.html) as your problem has less to do with tusd but is a general question about httpd proxy configuration. |
@Acconut Thx for your advice. |
Hi, I am trying to use this as described with reverse proxy. I have setup the reverse proxy which seems to be working as expected. I have 2 virtual host config files (one for http and other for https) in the https one...
I have changed the endpoint to match the reverse proxy which starts but then gives upload failed (mixed content errors showing in console) as it seems to reply with a non https file...
There is a catch all redirect on http vhost to https however this seems to ignore it. (or errors out without even trying).
If i manually try accessing https://tusd.[domain].net/files it correctly redirects to https and shows the "Method not supported" error from tusd which shows the reverse proxy is working fine. Using uppy javascript to upload, do not believe the problem is with this as default demo uses master.tus.io over https and this works fine. If I make no other changes but endpoint master.tus.io works fine and mine gives mixed content error. |
@Deck8 Please open a new issue for this question. |
currently, uploads to tusd fails because tusd is HTTP GETting chunk using non https url. We need to get it to use https url. the new settings is the recommended ones from tusd: tus/tusd#86
currently, uploads to tusd fails because tusd is HTTP GETting chunk using non https url. We need to get it to use https url. the new settings is the recommended ones from tusd: tus/tusd#86
currently, uploads to tusd fails because tusd is HTTP GETting chunk using non https url. We need to get it to use https url. the new settings is the recommended ones from tusd: tus/tusd#86
currently, uploads to tusd fails because tusd is HTTP GETting chunk using non https url. We need to get it to use https url. the new settings is the recommended ones from tusd: tus/tusd#86
currently, uploads to tusd fails because tusd is HTTP GETting chunk using non https url. We need to get it to use https url. the new settings is the recommended ones from tusd: tus/tusd#86
currently, uploads to tusd fails because tusd is HTTP GETting chunk using non https url. We need to get it to use https url. the new settings is the recommended ones from tusd: tus/tusd#86
currently, uploads to tusd fails because tusd is HTTP GETting chunk using non https url. We need to get it to use https url. the new settings is the recommended ones from tusd: tus/tusd#86
currently, uploads to tusd fails because tusd is HTTP GETting chunk using non https url. We need to get it to use https url. the new settings is the recommended ones from tusd: tus/tusd#86
currently, uploads to tusd fails because tusd is HTTP GETting chunk using non https url. We need to get it to use https url. the new settings is the recommended ones from tusd: tus/tusd#86
currently, uploads to tusd fails because tusd is HTTP GETting chunk using non https url. We need to get it to use https url. the new settings is the recommended ones from tusd: tus/tusd#86
sorry for so much questions and poor English.
I am running the binary on my server and I have a problem on implementing tusd on https. If I set the endpoint as https://localhost:1080/files/, an error occurred
but if I change the endpoint to https, another error occurred.
as I cannot modify the server config, I have to use https as the web protocol
I have no idea how to allow a https website to use tusd.
Thanks for your great help!
The text was updated successfully, but these errors were encountered: