timvisee / send

:mailbox_with_mail: Simple, private file sharing. Mirror of https://gitlab.com/timvisee/send

Home Page:https://send.vis.ee

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Transfer speed drops considerably as soon as the tab is not active

PostPollux opened this issue · comments

Hi! I use the latest docker container pulled a few days ago. Most things seem to work fine.

But I noticed the following:
When I upload a file and the tab is active I get the full 40mbit upload speed I currently have at my locaation. But as soon as I click on another tab in Firefox it drops to 6.2 mbit. If I use Chrome it drops to 13 mbit. If I use another service like swisstransfer.com the uploadspeed does not drop when I switch tabs. So it has to be something with the setup of the service.

I'm running it behind a nginx Reverse Proxy which handles the SSL Termination (JWilder Reverse Proxy). But that seems not to be the root of that issue, as I also tested to directly connect to the send instance without the proxy and without ssl and it was exactly the same issue.

By the way it is only happening with uploads, not with downloads.

Any idea what could be wrong or if there are any settings to fix that problem. The usage of the service is a bit unpleasant that way.
Hope someone has some input. Thanks.

Edit:
It seems to behave the same with https://send.vis.ee/ So it's probably not a problem of my setup.

commented

Hi! I use the latest docker container pulled a few days ago. Most things seem to work fine.

But I noticed the following: When I upload a file and the tab is active I get the full 40mbit upload speed I currently have at my locaation. But as soon as I click on another tab in Firefox it drops to 6.2 mbit. If I use Chrome it drops to 13 mbit. If I use another service like swisstransfer.com the uploadspeed does not drop when I switch tabs. So it has to be something with the setup of the service.

I'm running it behind a nginx Reverse Proxy which handles the SSL Termination (JWilder Reverse Proxy). But that seems not to be the root of that issue, as I also tested to directly connect to the send instance without the proxy and without ssl and it was exactly the same issue.

By the way it is only happening with uploads, not with downloads.

Any idea what could be wrong or if there are any settings to fix that problem. The usage of the service is a bit unpleasant that way. Hope someone has some input. Thanks.

Don't worry, I made the code a bit understanding for new users. Check out my send-reworked if you're having trouble and might want to build from source to make sure your instance is not vulnerable. https://github.com/WhateverItWorks/send-reworked

Don't worry, I made the code a bit understanding for new users. Check out my send-reworked if you're having trouble and might want to build from source to make sure your instance is not vulnerable. https://github.com/WhateverItWorks/send-reworked

Thanks for letting me know. Didn't know this repo existed. But still it didn't say anything about the issue I brought up and I think it does not provide any solution. I also tried the public hosted https://send.vis.ee/ and it seems to be the same there. So it is probably not a problem of my setup, but a problem of "send" in gerneral.

commented

Don't worry, I made the code a bit understanding for new users. Check out my send-reworked if you're having trouble and might want to build from source to make sure your instance is not vulnerable. https://github.com/WhateverItWorks/send-reworked

Thanks for letting me know. Didn't know this repo existed. But still it didn't say anything about the issue I brought up and I think it does not provide any solution. I also tried the public hosted https://send.vis.ee/ and it seems to be the same there. So it is probably not a problem of my setup, but a problem of "send" in gerneral.

Oh, maybe it's because of web socket support. If you're using NGINX, try to put into the location / area:

proxy_http_version 1.1;
   proxy_set_header Upgrade $http_upgrade;
   proxy_set_header Connection "Upgrade";
   proxy_set_header Host $host;

There's also this #156 issue that has been resolved, You can check it out!