SAML login issues suddenly from working install

Hi all,

Discourse version: [v2.4.0.beta2 +295]
Docker version: 19.03.1
OS: RHEL 7

I have been using discourse_saml for awhile now and as of today it is throwing a " Oops! That page doesn’t exist or is private." when trying to go to https://mydiscourse.url/discourse_saml login page.

The only error I could find in the logs was in production.log. I am seeing the following:

Started GET "/login.html" for 134.164.121.1 at 2019-08-16 16:09:20 +0000
Processing by StaticController#show as HTML
Parameters: {"id"=>"login"}
Rendering static/login.html.erb
Rendered static/login.html.erb (21.9ms)
Completed 200 OK in 23ms (Views: 22.4ms | ActiveRecord: 0.0ms)
Started GET "/session/csrf" for 134.164.121.1 at 2019-08-16 16:09:26 +0000
Processing by SessionController#csrf as JSON
Completed 200 OK in 2ms (Views: 0.3ms)
Started POST "/discourse_saml" for 134.164.121.1 at 2019-08-16 16:09:26 +0000
ActionController::RoutingError (No route matches [POST] "/discourse_saml")
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/actionpack- 
5.2.3/lib/action_dispatch/middleware/debug_exceptions.rb:65:in `call'
Rendering exceptions/not_found.html.erb within layouts/no_ember
Rendered exceptions/not_found.html.erb within layouts/no_ember (0.3ms)
Rendered layouts/_head.html.erb (0.4ms)
Rendered common/_discourse_stylesheet.html.erb (0.6ms)
Rendered application/_header.html.erb (0.4ms)
Rendering html template
Rendered html template (0.0ms)

I cannot find any other errors. Existing SAML tokens are still valid so users are able to log in but new sign ins get the 404 page.

For troubleshooting I have restarted the via the launcher, I have rebuilt using the launcher and issue persists. The discourse_saml plugin is up to date. As I mentioned, SAML was working fine and now its not for new sign ins, existing tokens are still valid and logging in.

Anyone able to point me a direction? Thanks!