Very strange 502 error still

Unfortunately, it isn’t a Ruby problem :frowning: It is a conflict we are experiencing and that’s about as much detail as I’ll go into at this moment. We have the dev team working on it, it isn’t an easy fix and is requiring a lot of time.

1 Like