Immediate upload failure (something went wrong page) about send HOT 9 OPEN

I have this exact same issue both running as a normal npm app and as a container.

from send.

OK. I found a solution. Open server/config.js in any editor and change this line:

fxa_required: { format: Boolean, default: true, env: 'FXA_REQUIRED' },
to:

fxa_required: { format: Boolean, default: false, env: 'FXA_REQUIRED' },

from send.

It worked for me

from send.

Me too - How'd you find the fix? Someone else posted a new 401 error with that as an ENV variable. Couldn't find it in the docs, but I'm sure that's just b/c i'm skimming. It also makes sense since they're changing how the service can be used to mandate auth...

from send.

Well, let me explain, take a look at this code where the 401 error occurs:

if (config.fxa_required && !user) { ws.send( JSON.stringify({ error: 401 }) ); return ws.close(); }(taken from https://github.com/mozilla/send/blob/master/server/routes/ws.js)


So, it checks if a FXA(Firefox Account) is required and if the client is not authenticated, it gives an error.


In the configuration, Firefox Accounts are required by default but you need a client ID for that and we don't have any.


That's why this happens.

from send.

Well, let me explain, take a look at this code where the 401 error occurs:

if (config.fxa_required && !user) { ws.send( JSON.stringify({ error: 401 }) ); return ws.close(); }(taken from https://github.com/mozilla/send/blob/master/server/routes/ws.js)

So, it checks if a FXA(Firefox Account) is required and if the client is not authenticated, it gives an error.

In the configuration, Firefox Accounts are required by default but you need a client ID for that and we don't have any.

That's why this happens.

With you - except where I saw the error in my console was...I think storage.js or something weird, leading me to think it was some undocumented storage req. I also could be remembering wrong so will have to play a bit later... You just tried to submit something and then watched the console?

In any event...thank you!

from send.

I looked at the network activity and saw the 401 error

from send.

Thanks @okyanusoz! Excited to try it out.

from send.

I tried setting the environment variable FXA_REQUIRED to false (which is the format convict expects for boolean env vars) and it didn't help.

from send.