Maintenance still going on?? All feeds are still down today

edit

E, [2022-08-17T15:11:05.303855 #61] ERROR -- : Error while querying RETS, moving onto next query, data: {"error"=>"Got error code 20036 (miscellaneous server error.)"

Are you still having issues with this?

@bwolven yes...we have 100+ MLSs still not updating

So you are getting the error when trying to search but the login is working?
If so, review the question "Paragon Outage" and see if you have a similar setting.

looking

@bwolven Our dev team did some digging using the info from Paragon Outage and found:

You are sending us this as a cookie session (note the two elements in the array) ["RETS-Session-ID=-c1a2c6c4-c009-4627-bb66-8f4b9eadfdf3-; path=/", "TS01b4ff87=01689bcfc5116b21c43264d99fc26dd81d358a7e1d377ab268e9fd0f93e75f3e9ab9c11142c0cc99f94a7dfa5391ae3cf98da96c50aca8b2632b8224cc89ff119415516e7a; Path=/"]

It looks like you changed the way how you are sending cookie sessions/handling them in the subsequent requests. Basically "TS01b4ff87=01689bcfc5116b21c43264d99fc26dd81d358a7e1d377ab268e9fd0f93e75f3e9ab9c11142c0cc99f94a7dfa5391ae3cf98da96c50aca8b2632b8224cc89ff119415516e7a; Path=/" is breaking the auth.

We are making a change on our end to handle this short term but it looks like during the maintenance window last night a change to cookie handling was also included. The change we are making is not an ideal long-term solution. Is this something you can take back to your team and address?

I have no idea what this "TS01b4ff87=" portion of the cookie is used for.
I haven't noticed it before but I haven't really looked at the cookies for a while.

I wonder if your client library isn't handling possible multiple cookies properly.
What I see coming from the server is:

Set-Cookie: RETS-Session-ID=-371db403-044f-4b4e-8a9c-7a13472cb2a3-; path=/
Set-Cookie: TS01b4ff87=01689bcfc5c6023ecae275e39b8631f5b9d3e50417f8a5f1969feb1766c12b1de27f0d5d601dfb844196f127f892ae83f21b8a2aef3bd48e64dc63d092880a2cc480f27d84; Path=/

And LIBRETS client sends the Cookie back as:

Cookie: RETS-Session-ID=-371db403-044f-4b4e-8a9c-7a13472cb2a3-; TS01b4ff87=01689bcfc5c6023ecae275e39b8631f5b9d3e50417f8a5f1969feb1766c12b1de27f0d

We're also seeing the "miscellaneous server error" from queries. If paragon is going to change how the feed is handling cookies at least send out a notice so we can have the code updates done in advance to handle these changes.

You will get the "miscellaneous server error" if the RETS-Session in the Cookie isn't being sent back correctly.
If we can't get the RETS-Session-ID value we can't link the request to the proper user.

Were you able to get your feeds back working again?