<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Hi Ryan,<br>
<br>
thank you for your response. Yes, it was a misconfiguration
issue. Possbily it would be helpful to have a set of super-global
env variables for configuration of all of the parts of the Sync /
Accounts / Auth / oAuth / Profile Server solution. This was my
fault, have the same env variable that needs different content for
each part.<br>
<br>
<br>
Bye<br>
<br>
Uwe<br>
<br>
Am 08.05.2018 um 00:20 schrieb Ryan Kelly:<br>
</div>
<blockquote type="cite"
cite="mid:CAB3n-YZMGPxTqmc19PEmVWrmjaaTw4T7F+GFKWN=hxdsKv5cpA@mail.gmail.com">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote"><br>
</div>
<div class="gmail_quote">Hi Uwe, thanks for reaching out.
Reponses inline below.</div>
<div class="gmail_quote"><br>
</div>
<div class="gmail_quote">On 8 May 2018 at 05:09, <a
href="mailto:dev-fxacct@gmx-topmail.de"
moz-do-not-send="true">dev-fxacct@gmx-topmail.de</a> <span
dir="ltr"><<a href="mailto:dev-fxacct@gmx-topmail.de"
target="_blank" moz-do-not-send="true">dev-fxacct@gmx-topmail.de</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF">
<p>Hello,</p>
<p>after setting up my own Accounts Server (with Content
Server, oAuth Server und Sync Server) I get the error
message about "missingFlowId". Why?</p>
</div>
</blockquote>
<div><br>
</div>
<div>The server will occasionally log things a `ERROR` level
but still function correctly, and the missingFlowId is one
example. Does the server setup still work correctly? If
not, what error messages or other failures do you see in
Firefox when trying to use it?<br>
</div>
<div> </div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF">fxa-auth-server.INFO: stat
{"stat":"scrypt","maxPending":0,"numPending":0,"numPendingHWM":0}<br>
<p> fxa-auth-server.DEBUG: server.onRequest<br>
fxa-auth-server.INFO: request.summary
{"op":"request.summary","code"<wbr>:404,"errno":999,"rid":"<wbr>1525718907848:linux-box:7129:<wbr>jgtxgn8h:10054","path":"/<wbr>bundle-<wbr>ba35c2d66b86a6485c3243f4ca7d12<wbr>1be2c892c9/appDependencies.<wbr>bundle.js","agent":"Mozilla/5.<wbr>0
(X11; Linux x86_64; rv:59.0) Gecko/20100101
Firefox/59.0","t":2,"uid":"00"<wbr>}<br>
</p>
</div>
</blockquote>
<div><br>
</div>
<div>The request path here ("/bundle-ba35..") looks like
it's supposed to be a request to fetch javascript from the
content-server, but is being received and handled by the
auth-server. I wonder if there's an error in
configuration of your reverse proxy that is sending this
request to the wrong backend server.<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
<div bgcolor="#FFFFFF">
<p> fxa-auth-server.ERROR: metricsEvents.emitFlowEvent
{"op":"metricsEvents.<wbr>emitFlowEvent","event":"route.<wbr>/bundle-<wbr>ba35c2d66b86a6485c3243f4ca7d12<wbr>1be2c892c9/appDependencies.<wbr>bundle.js.404.999","<wbr>missingFlowId":true}<br>
</p>
</div>
</blockquote>
<div><br>
</div>
<div>The server is trying to log a metrics event indicating
that the client requested a particular path, and it
expects to find a "metricsContext" request parameter to
help it do so. But because this request is going to the
wrong server, it doesn't have the "metricsContext"
parameter, and the server logs an error. This error isn't
fatal though, the server will still process the request -
in this case, by returning a "404 not found".</div>
<div><br>
</div>
<div>It seems a little weird that we try to log metrics
events on non-existent routes, so I filed a bug to follow
up:</div>
<div><br>
</div>
<div> <a
href="https://github.com/mozilla/fxa-auth-server/issues/2423"
moz-do-not-send="true">https://github.com/mozilla/fxa-auth-server/issues/2423</a></div>
<div><br>
</div>
<div>But as noted above, I think this is ultimately caused
by some mis-configuration of your reverse proxy that is
sending requests to the wrong backend server.</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div> Cheers,</div>
<div><br>
</div>
<div> Ryan<br>
</div>
</div>
<br>
</div>
</div>
</blockquote>
<p><br>
</p>
</body>
</html>