This seems like one of the API VMs got a bit discombobulated in routing. I've encouraged xen to rethink its routing and it seems to be working now.
Doug Bell [email protected] > On Dec 13, 2017, at 8:22 AM, Nigel Horne <[email protected]> wrote: > > I'm seeing errors such as this - any thoughts? I'm seeing it on all of my > clients and I've "not changed a thing (TM)". > > <html> > <HEAD><TITLE>Error: Bad Request</TITLE></HEAD> > <BODY> > <H1>Error: Bad Request</H1> > write error 104: Connection reset by peer > <small>This is a client error, not a server error.</small> > </BODY> > </HTML> > > > -Nigel > > -- > Nigel Horne > Conductor: Rockville Brass Band, Washington Metropolitan GSO > @nigelhorne | fb/nigel.horne | bandsman.co.uk | concert-bands.co.uk | > www.nigelhorne.com > > Unless it's for my eyes only, please use "reply all"
signature.asc
Description: Message signed with OpenPGP
