search

timvisee / send

:mailbox_with_mail: Simple, private file sharing. Mirror of https://gitlab.com/timvisee/send
https://send.vis.ee
Mozilla Public License 2.0
4.6k stars 261 forks source link

Password is not working #61

Open hamza-younas94 opened 2 years ago

hamza-younas94 commented 2 years ago

We are using send on self hosted with docker when we uploading files with "Protect with password" we are getting error during file download that "Password is incorrect".

Any idea? I have followed the same instructions.

timvisee commented 2 years ago

That's weird. Not sure what is going on here.

If you're using Redis, could you confirm the configuration is correct? If you're using Docker containers, restart all of them (Redis and Send), and see if non-password protected files are still downloadable.

emilyboda commented 2 years ago

I'm also having an issue where my password is invalid. I've tried twice and double-checked my password both times. I'm using the web app on both ends (sending and receiving).

timvisee commented 2 years ago

I'm also having an issue where my password is invalid. I've tried twice and double-checked my password both times. I'm using the web app on both ends (sending and receiving).

I this on the hosted instance, or are you running an instance yourself?

emilyboda commented 2 years ago

No I am using the website

Emily J. Boda

@.*** (202) 725-1236 emilyboda.com

On Thu, May 12, 2022, 2:39 PM Tim Visée @.***> wrote:

I'm also having an issue where my password is invalid. I've tried twice and double-checked my password both times. I'm using the web app on both ends (sending and receiving).

I this on the hosted instance, or are you running an instance yourself?

— Reply to this email directly, view it on GitHub https://github.com/timvisee/send/issues/61#issuecomment-1125308758, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACF6ZX64JVV4N25W3AGAIRTVJVF7PANCNFSM5K3V6EUA . You are receiving this because you commented.Message ID: @.***>

timvisee commented 2 years ago

No I am using the website

Note that correct capitalization is important.

What browser and device are you using?

birlorg commented 2 years ago

I just tested https://send.vis.ee and set a password, worked fine.

Tested using these browsers:

No issues to report.

soflane commented 2 years ago

I am facing the same problem with a self hosted instance (redis is enabled)

soflane commented 2 years ago

Just figured it out after ! I had configured the environment variable BASE_URL without the starting 'https://' in my docker-compose and .env file

I am facing the same problem with a self hosted instance (redis is enabled)

giang12 commented 2 years ago

hum weird.. consistently getting this error when DETECT_BASE_URL=true ..

TheFiZi commented 2 years ago

Same issue.

I run a single instance of send but reverse proxy to it via nginx from 3 separate domains.

If I set DETECT_BASE_URL=true passwords don't work but file downloads have the correct URL and non-passworded downloads work fine.

If I set DETECT_BASE_URL=false passworded downloads work fine but all URLs generated are for the domain I have configured in base_url

kda-jt commented 1 year ago

I'm having the same issue. The solution suggested by @TheFiZi is a valid workaround. Thanks mate!

l4rm4nd commented 11 months ago

Just figured it out after ! I had configured the environment variable BASE_URL without the starting 'https://' in my docker-compose and .env file

I am facing the same problem with a self hosted instance (redis is enabled)

That was the solution in my case.

I was running a selfhosted instance (docker) and forgot the protocol handler in BASE_URL. Now works flawlessly.

Example compose file here.

PatCas71 commented 7 months ago

Just figured it out after ! I had configured the environment variable BASE_URL without the starting 'https://' in my docker-compose and .env file

I am facing the same problem with a self hosted instance (redis is enabled)

That was the solution in my case.

I was running a selfhosted instance (docker) and forgot the protocol handler in BASE_URL. Now works flawlessly.

Example compose file here.

Hi l4rm4nd can you provide tour .env too, i always have an error when uploading with you conpose file. Thanks! ;)

l4rm4nd commented 7 months ago

Just figured it out after ! I had configured the environment variable BASE_URL without the starting 'https://' in my docker-compose and .env file

I am facing the same problem with a self hosted instance (redis is enabled)

That was the solution in my case.

I was running a selfhosted instance (docker) and forgot the protocol handler in BASE_URL. Now works flawlessly.

Example compose file here.

Hi l4rm4nd can you provide tour .env too, i always have an error when uploading with you conpose file. Thanks! ;)

Hey, the provided compose file is complete. All environment variables are defined in the environment section.

You likely have a permission error as my compose example uses bind mounts. Please check the /mnt/docker-volumes/send path for proper read+write permissions.

Use chown/chmod as necessary.

PatCas71 commented 7 months ago

Just figured it out after ! I had configured the environment variable BASE_URL without the starting 'https://' in my docker-compose and .env file

I am facing the same problem with a self hosted instance (redis is enabled)

That was the solution in my case. I was running a selfhosted instance (docker) and forgot the protocol handler in BASE_URL. Now works flawlessly. Example compose file here.

Hi l4rm4nd can you provide tour .env too, i always have an error when uploading with you conpose file. Thanks! ;)

Hey, the provided compose file is complete. All environment variables are defined in the environment section.

You likely have a permission error as my compose example uses bind mounts. Please check the /mnt/docker-volumes/send path for proper read+write permissions.

Use chown/chmod as necessary.

Wow that is fast!! :) Big thanks for your help!

What are the permissions i shoud give to stay secure and make it work? that's what i have: ls -lah /mnt/docker-volumes/send/ total 16K drwxr-xr-x 4 root root 4.0K Feb 24 09:23 . drwxr-xr-x 3 root root 4.0K Feb 24 09:23 .. drwxr-xr-x 2 systemd-coredump root 4.0K Feb 24 09:36 redis drwxr-xr-x 2 root root 4.0K Feb 24 09:23 uploads

l4rm4nd commented 7 months ago

Just figured it out after ! I had configured the environment variable BASE_URL without the starting 'https://' in my docker-compose and .env file

I am facing the same problem with a self hosted instance (redis is enabled)

That was the solution in my case. I was running a selfhosted instance (docker) and forgot the protocol handler in BASE_URL. Now works flawlessly. Example compose file here.

Hi l4rm4nd can you provide tour .env too, i always have an error when uploading with you conpose file. Thanks! ;)

Hey, the provided compose file is complete. All environment variables are defined in the environment section.

You likely have a permission error as my compose example uses bind mounts. Please check the /mnt/docker-volumes/send path for proper read+write permissions.

Use chown/chmod as necessary.

Wow that is fast!! :) Big thanks for your help!

What are the permissions i shoud give to stay secure and make it work? that's what i have: ls -lah /mnt/docker-volumes/send/ total 16K drwxr-xr-x 4 root root 4.0K Feb 24 09:23 . drwxr-xr-x 3 root root 4.0K Feb 24 09:23 .. drwxr-xr-x 2 systemd-coredump root 4.0K Feb 24 09:36 redis drwxr-xr-x 2 root root 4.0K Feb 24 09:23 uploads

Everything in the upload folder should be encrypted on rest so it does not really matter. You could use 777 if you don't care.

The container uses the user app with UID 1000 though and likely writes into the upload folder with this UID too.

So this should be sufficient:

sudo chown -R 1000: /mnt/docker-volumes/send/*

sudo chmod -R 775 /mnt/docker-volumes/send/*

Adjust to your level of paranoia and your infrastructure setup (maybe you use NFS share mounted at /mnt) 😉

PatCas71 commented 7 months ago

Just figured it out after ! I had configured the environment variable BASE_URL without the starting 'https://' in my docker-compose and .env file

I am facing the same problem with a self hosted instance (redis is enabled)

That was the solution in my case. I was running a selfhosted instance (docker) and forgot the protocol handler in BASE_URL. Now works flawlessly. Example compose file here.

Hi l4rm4nd can you provide tour .env too, i always have an error when uploading with you conpose file. Thanks! ;)

Hey, the provided compose file is complete. All environment variables are defined in the environment section. You likely have a permission error as my compose example uses bind mounts. Please check the /mnt/docker-volumes/send path for proper read+write permissions. Use chown/chmod as necessary.

Wow that is fast!! :) Big thanks for your help! What are the permissions i shoud give to stay secure and make it work? that's what i have: ls -lah /mnt/docker-volumes/send/ total 16K drwxr-xr-x 4 root root 4.0K Feb 24 09:23 . drwxr-xr-x 3 root root 4.0K Feb 24 09:23 .. drwxr-xr-x 2 systemd-coredump root 4.0K Feb 24 09:36 redis drwxr-xr-x 2 root root 4.0K Feb 24 09:23 uploads

Everything in the upload folder should be encrypted on rest so it does not really matter. You could use 777 if you don't care.

The container uses id 1000 through and likely writes into the upload folder with this UID too.

sudo chown -R 1000: /mnt/docker-volumes/send/*

sudo chmod -R 775 /mnt/docker-volumes/send/*

Adjust to your level of paranoia and your infrastructure setup (maybe you use NFS share mounted at /mnt) 😉

It work now! Again, big thanks for your help!!

brknkfr commented 7 months ago

I just encountered the same error. In my case it was the missing proxy_set_header X-Forwarded-Proto $scheme; in the front end nginx proxy.