RBE post didn't go through
Replied by email to forum thread, using iPad. This thread -- https://commons.gc.cuny.edu/groups/cac-faculty-fellows/forum/topic/add-users-sidebar-widget-disappeared/#post-53857. Didn't go through.
Screenshot of sent email attached.
#2 Updated by Luke Waltzer over 4 years ago
- File Screen Shot 2017-03-07 at 10.03.18 AM.png Screen Shot 2017-03-07 at 10.03.18 AM.png added
- Priority name changed from Normal to Urgent
Elevating priority... confirmed RBE is not working on another thread -- https://commons.gc.cuny.edu/groups/coursetest/forum/topic/testing-rbe/#post-53858.
Screenshot of email attached.
#3 Updated by Luke Waltzer over 4 years ago
Just got four emails from this post -- https://commons.gc.cuny.edu/groups/digital-humanities-initiative/forum/topic/fwd-invitation-to-digital-paxton-launch-events-2/.
And then just got four rejection messages each for my earlier replies.
Unfortunately, your reply to the forum topic could not be posted because it appears you have already made the same reply.
Here is a copy of your reply:
We apologize for any inconvenience this may have caused.
#5 Updated by Raymond Hoh over 4 years ago
So the problem is the remote POST response used to trigger RBE is no longer responding:
I'm guessing IT has put in some security restrictions on POST responses. For the moment, I have manually triggered RBE. I'll look into adding some code that doesn't use a POST response to trigger RBE on the RBE settings page.
#8 Updated by Raymond Hoh over 4 years ago
I've written some new logic so RBE can spawn new inbox checks from the RBE admin settings page.
This approach doesn't use a loopback POST response as before, but instead uses AJAX to do the initial ping.
The good thing is this approach will probably stop our problem with RBE duplicate posts from occurring since you can only spawn new inbox checks from the admin settings page and not on a pageload basis like before.
The problem is if the Commons goes down or if RBE isn't able to connect to the inbox during a scheduled ping, someone will need to manually go to the RBE admin settings page and hit the "Connect" button.
To remedy this, I can write a task hooked to WP cron (perhaps run hourly) to check if RBE is connected. If RBE isn't connected, it can email some of us to go to the RBE settings page and re-connect.
FYI: This code is live on the Commons, but I haven't committed it to the CAC repo yet as I'm still monitoring things, but initial logs look good on my end.
It might be good to ping Lihua just to see what has changed exactly or to see if something like fail2ban is blocking the loopback POST response.
#9 Updated by Raymond Hoh over 4 years ago
- Status changed from In Progress to Resolved
- Target version set to 1.10.13
Boone - I've added the updated RBE code to 1.10.x branch:
And on production, I have cherry-picked the commit. RBE is already up-and-running; you shouldn't have to do anything for the maintenance release today.
One thing I haven't done is write a task hooked to WP cron to email one of us should the IMAP connection go down, but I can do this before the next maintenance release on the 21st.
Going to mark this as resolved.