# Creating a Send File does Not work from browser extension **URL:** \ **Category:** Help\ **Created:** [May 17, 2021, 12:10pm UTC](https://vaultwarden.discourse.group/t/creating-a-send-file-does-not-work-from-browser-extension/901 "2021-05-17T12:10:38Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![PaperOrin](https://avatars.discourse-cdn.com/v4/letter/p/5fc32e/32.png) [@PaperOrin](https://vaultwarden.discourse.group/u/PaperOrin)\ **Post date:** [May 17, 2021, 12:10pm UTC](https://vaultwarden.discourse.group/t/creating-a-send-file-does-not-work-from-browser-extension/901/1 "2021-05-17T12:10:38Z")
The Send text feature works but the Send file feature does not work, when created from a browser extension (tried Firefox and Chrome). It also does not work from iOS app. Doesn’t look like there are any updates to the browser extensions. I believe the docker is running the latest image. It does work if you log into the webpage and create the Send file that way. The log shows this: [2021-05-17 08:01:12.816][request][INFO] POST /api/sends/file/v2 [2021-05-17 08:01:12.816][response][INFO] 404 Not Found Versions Server Installed Ok 1.21.0 Server Latest 1.21.0 Web Installed 2.19.0d Database SQLite: 3.33.0 ### Checks Running within Docker **Yes** Uses a reverse proxy **Yes** IP header Match **Config/Server:** X-Real-IP Internet access Ok **Yes** Internet access via a proxy **No** DNS ([github.com](http://github.com)) Ok Date & Time (UTC) Ok Domain configuration Match HTTPS ---
**Author:** ![jjlin](https://avatars.discourse-cdn.com/v4/letter/j/e19adc/32.png) [@jjlin](https://vaultwarden.discourse.group/u/jjlin)\ **Post date:** [May 17, 2021, 7:44pm UTC](https://vaultwarden.discourse.group/t/creating-a-send-file-does-not-work-from-browser-extension/901/2 "2021-05-17T19:44:50Z")
I believe the v2 API is from the new browser extension version released a few days ago, and it’s a known issue that Vaultwarden is missing this new API. But the extension should be falling back to the older API for now: ```nohighlight [2021-05-17 18:21:24.840][request][INFO] POST /api/sends/file/v2 [2021-05-17 18:21:24.840][response][INFO] 404 Not Found [2021-05-17 18:21:24.950][request][INFO] POST /api/sends/file [2021-05-17 18:21:24.951][multipart::server][INFO] Multipart::with_boundary(_, "----WebKitFormBoundary...") [2021-05-17 18:21:24.956][response][INFO] POST /api/sends/file multipart/form-data (post_send_file) => 200 OK ``` ---
**Author:** ![PaperOrin](https://avatars.discourse-cdn.com/v4/letter/p/5fc32e/32.png) [@PaperOrin](https://vaultwarden.discourse.group/u/PaperOrin)\ **Post date:** [May 17, 2021, 8:21pm UTC](https://vaultwarden.discourse.group/t/creating-a-send-file-does-not-work-from-browser-extension/901/3 "2021-05-17T20:21:47Z")
Thank you for the reply. Do you mean I should do something to the extension to make it revert back to the v1? Or do you mean I should try and install an older version of the extension? ---
**Author:** ![jjlin](https://avatars.discourse-cdn.com/v4/letter/j/e19adc/32.png) [@jjlin](https://vaultwarden.discourse.group/u/jjlin)\ **Post date:** [May 17, 2021, 9:11pm UTC](https://vaultwarden.discourse.group/t/creating-a-send-file-does-not-work-from-browser-extension/901/4 "2021-05-17T21:11:29Z")
I mean that it works fine for me on version 1.50.0 of the browser extension. Are you sure there’s no `POST /api/sends/file` afterwards, as in my log above? ---
**Author:** ![PaperOrin](https://avatars.discourse-cdn.com/v4/letter/p/5fc32e/32.png) [@PaperOrin](https://vaultwarden.discourse.group/u/PaperOrin)\ **Post date:** [May 17, 2021, 9:42pm UTC](https://vaultwarden.discourse.group/t/creating-a-send-file-does-not-work-from-browser-extension/901/5 "2021-05-17T21:42:35Z")
I confirmed I am running Version 1.50.0 of the extension on firefox (for this test). This is all that appears in the log (set to info). **Previous line is unrelated** [2021-05-17 17:38:08.229][request][INFO] POST /api/sends/file/v2 [2021-05-17 17:38:08.229][response][INFO] 404 Not Found **next line is blank.** attached is a screenshot of the error on the extension ![extension-error](https://global.discourse-cdn.com/free1/uploads/vaultwarden/original/1X/fd4f907e91245a58e76aad856e81374bb2ed28c2.jpeg) ---
**Author:** ![jjlin](https://avatars.discourse-cdn.com/v4/letter/j/e19adc/32.png) [@jjlin](https://vaultwarden.discourse.group/u/jjlin)\ **Post date:** [May 17, 2021, 10:00pm UTC](https://vaultwarden.discourse.group/t/creating-a-send-file-does-not-work-from-browser-extension/901/6 "2021-05-17T22:00:47Z")
A 405 error suggests you’ve configured your reverse proxy to block an HTTP method it shouldn’t be blocking, though if you’re blocking `POST`, a lot of obvious things wouldn’t work, so maybe it’s returning 405 when blocking some other aspect of a request. ---
**Author:** ![PaperOrin](https://avatars.discourse-cdn.com/v4/letter/p/5fc32e/32.png) [@PaperOrin](https://vaultwarden.discourse.group/u/PaperOrin)\ **Post date:** [May 17, 2021, 10:55pm UTC](https://vaultwarden.discourse.group/t/creating-a-send-file-does-not-work-from-browser-extension/901/7 "2021-05-17T22:55:50Z")
I think you’re right. Something with the reverse proxy. When I connect directly using the internal IP over 80, I have no problems. ---
**Author:** ![PaperOrin](https://avatars.discourse-cdn.com/v4/letter/p/5fc32e/32.png) [@PaperOrin](https://vaultwarden.discourse.group/u/PaperOrin)\ **Post date:** [May 17, 2021, 11:11pm UTC](https://vaultwarden.discourse.group/t/creating-a-send-file-does-not-work-from-browser-extension/901/8 "2021-05-17T23:11:32Z")
Reverting back to extension version 1.49.1 (firefox) makes it all work, again. Sounds like it’s what you were thinking with the v2 API, in extension 1.50? I’ll stick with the older extension for now. Thanks for all the help. ---
**Author:** ![BlackDex](https://yyz2.discourse-cdn.com/free1/user_avatar/vaultwarden.discourse.group/blackdex/32/8_2.png) [@BlackDex](https://vaultwarden.discourse.group/u/BlackDex)\ **Post date:** [May 18, 2021, 6:47am UTC](https://vaultwarden.discourse.group/t/creating-a-send-file-does-not-work-from-browser-extension/901/9 "2021-05-18T06:47:58Z")
I have v1.50.0 running, and it works without issues. So, there is something triggering some blocking on your reverse proxy side either by not allowing POST to some paths, or it triggers some kind of WAF protection because of the first attempt to the `v2` path that fails.