After rebuild empty Windows.

[misterhsp]

I rebuilt the servers again today. But now I only get an empty window at Manage Devices/Accounts, new login doesn't work either, also empty window. Is there something broken or have you changed something I should know?

Thanks Holger...

[misterhsp]

auth and oauth-server from the last backup of the docker images solves the problem. The backup is about 1 week old.

[misterhsp]

Something doesn't work properly between auth and oauth-server anymore. From my backup of auth/outh everything is fine.

[clouserw]

We're currently merging the auth and oauth servers, but I don't know if that would affect what you're trying to do. I don't think there is anything actionable for us here so I'm closing this Issue.

[misterhsp]

Too bad, I would like to continue using fxa-selfhosting. But I only get empty windows from the content-server. something with the auth and oauth-server doesn't work here anymore.

...

[clouserw]

@dannycoates what config changes did we end up having to make here?

[misterhsp]

I have all Dockerimages freshly built with current git-repo. Nothing to do, I can't get it to work anymore. I don't understand why Mozilla has to change things forever if everything works. Sometime I throw Firefox away and take Chrome from Google if fxa-selfhosting is no longer transparent for the user.

[misterhsp]

When creating a new account I get the following red background. "Invalid parameter: redirectTo"

That's all it's gonna take.

[misterhsp]

Then I will say goodbye to Mozilla and Firefox, since no help is to be expected.

bye

[misterhsp]

When creating a new account I get the following red background. "Invalid parameter: redirectTo"

Does anyone else have a comment on this?

[shane-tomlinson]

Then I will say goodbye to Mozilla and Firefox, since no help is to be expected. bye

I understand the frustration, however comments like the above are not conducive to getting help. We help out with support where and when we can, but support is not our top priority and sometimes questions go unanswered.

Does anyone else have a comment on this?

From what it looks like, one of these two validation rules believes something is invalid:

• https://github.com/mozilla/fxa/blob/74f6f333c5d687a4b740238f53c8b119553f0037/packages/fxa-content-server/app/scripts/models/reliers/oauth.js#L52
• https://github.com/mozilla/fxa/blob/74f6f333c5d687a4b740238f53c8b119553f0037/packages/fxa-content-server/app/scripts/models/reliers/relier.js#L77

Without understanding how your local install is setup, I can't say which.

[misterhsp]

Here is my docker-startscript and nginx.conf. As already mentioned, with older auth and outh-server everything works fine.

docker-startscript: https://pastebin.com/nZ9r2Tzm

nginx.conf: https://pastebin.com/T0Fqy3UN

[misterhsp]

What else do you need for information, I can't get it going with newer auth and oauth servers?

Thank you...

[shane-tomlinson]

@misterhsp when you load FxA, do you see anything in the developer console? Or the network console? What is the flow you are going through to see the error?

[misterhsp]

Am 23.10.19 um 09:13 schrieb Shane Tomlinson:

@misterhsp https://github.com/misterhsp when you load FxA, do you see anything in the developer console? Or the network console? What is the flow you are going through to see the error?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/mozilla/fxa/issues/2763?email_source=notifications&email_token=AKGJLRJCG5NTSOWOEK7QNK3QP72SPA5CNFSM4I5245W2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECAK46Q#issuecomment-545304186, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKGJLRPW4L7SBUXSNRVWT4DQP72SPANCNFSM4I5245WQ.

I am looking for errors in the logs of the dockerimages 'docker logs -f foo'. But I don't find any errors there. What do you mean by developer / network console?

[shane-tomlinson]

What do you mean by developer / network console?

In Firefox (or Chrome) if you press F12 on your keyboard, the developer tools will pop up. One tab will be labelled "Console" and prints error messages. Another is "Network" and shows all the network activity.

[misterhsp]

Am 23.10.19 um 11:12 schrieb Shane Tomlinson:

What do you mean by developer / network console?

In Firefox (or Chrome) if you press F12 on your keyboard, the developer tools will pop up. One tab will be labelled "Console" and prints error messages. Another is "Network" and shows all the network activity.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/mozilla/fxa/issues/2763?email_source=notifications&email_token=AKGJLRNCJ7II2DQF5DCPFVTQQAIPDA5CNFSM4I5245W2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECAVZPY#issuecomment-545348799, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKGJLRJPM7MDRAZU7QMX3HDQQAIPDANCNFSM4I5245WQ.

I found an HTTP 500 error. See attached network.png. Is it possible to save the whole content in the network console?

[misterhsp]

The picture hasn't arrived yet. Therefore once again like this.

https://imgur.com/a/THP8Yv6

...

[misterhsp]

I can't resolve what's going wrong. Strange is only that with the backup of auth / oauth server everything works fine. They are almost 4 weeks old.

[misterhsp]

after a double click on the error this is displayed.

code | 401 errno | 110 error | "Unauthorized" message | "Invalid authentication token: Missing authentication" info | "https://github.com/mozil…s/api.md#response-format"

But why is that invalid? Maybe something is broken in the sql database?

[misterhsp]

Doesn't anyone have any idea what's not working for me?

[shane-tomlinson]

The request is failing making a /token request on the auth-server. The /token endpoint on the auth server makes a backend request to the oauth-server to get an access token. It could be that your OAuth server has not started or has stopped running. Can you check that the OAuth server is still running? There may be a clue in the logs as to why it's not starting.

[misterhsp]

Am 24.10.19 um 14:45 schrieb Shane Tomlinson:

The request is failing making a |/token| request on the auth-server. The /token endpoint on the auth server makes a backend request to the oauth-server to get an access token. It could be that your OAuth server has not started or has stopped running. Can you check that the OAuth server is still running? There may be a clue in the logs as to why it's not starting.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/mozilla/fxa/issues/2763?email_source=notifications&email_token=AKGJLRLSYA3JD7APGTUG22LQQGKGPA5CNFSM4I5245W2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECE4QDI#issuecomment-545900557, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKGJLRLL45PI5WZ6W6S67KDQQGKGPANCNFSM4I5245WQ.

auth and oauth both run. I have attached the logs of both times. I just don't get why it works with the older servers and not with the new ones.

I happened to find a CRITICAL error in the auth-server. Why port 3306 is suddenly no longer reached by SQL is a mystery to me.

grep CRITICAL auth.txt fxa-oauth-server.bin.server.CRITICAL: db.ping {"cause":"Error: connect ECONNREFUSED 127.0.0.1:3306","isOperational":true,"errno":"ECONNREFUSED","code":"ECONNREFUSED","syscall":"connect","address":"127.0.0.1","port":3306,"fatal":true}

auth https://pastebin.com/0c42V5Nn

oauth https://pastebin.com/hvVfdmgr

[misterhsp]

I think by now this is probably a bug in the auth or oauth server. How can I reopen this bug report?

[shane-tomlinson]

@misterhsp and I have taken this to email to avoid divulging sensitive information publicly.