Hello @joshua,
I enabled debug on the CORS filter and in the CORS event log we could see a mismatch of protocols http vs http. I then added the headers that RobotDan has mentioned in other posts and now when we login instead of getting a 403, we get a 404 from Nginx that /oauth2/authorize does not exist. Is getting a 404 at this point expected? With this configuration there is nothing logged so I am assuming the previous 403 was from a CORS error but now this 404 is unclear to us.

Thanks @dan. We actually do have a kickstart file in place in our Helm chart but in the case that we want to start fresh, I assumed that deleting our Helm chart which includes our Postgresql DB would do just that, but that assumption is incorrect. So far the only way I have found to start fresh is to delete the EKS cluster and rebuild from the ground up.

How do you completely delete fusionAuth in order to get a fresh installation? I have deleted the helm charts but when I redeploy all my previous history is still intact. So far the only way I have found to get a clean slate is to delete my kubernetes cluster and reinstall, which is time consuming.

I am using the latest helm chart and passing in the connection string for our Elastic server. However during provisioning I receive a 401 http response and it appears the credentials were dropped from the connection string. Has anyone seen this before? This is with FusionAuth 1.19.0. I did not have this problem with 1.16.1. If I login to the fusionAuth pod I can see the credential string setup properly as the SEARCH_SERVERS and I can manually connect to ElasticSearch using it:

SEARCH_SERVERS=http://elastic:V9Q1nbqUK82caeche6514i0i@elasticsearch-cluster-es-http:9200
(that is a temporary password)

2020-09-23 12:57:55.025 PM INFO com.inversoft.search.ElasticRestClientHelper - Connecting to Elasticsearch at [http://elasticsearch-cluster-es-http:9200]
2020-09-23 12:57:55.614 PM INFO com.inversoft.maintenance.search.ElasticsearchMaintenanceModeSearchService - Missing search index [fusionauth_user]
2020-09-23 12:57:55.620 PM INFO com.inversoft.search.ElasticRestClientHelper - Connecting to Elasticsearch at [http://elasticsearch-cluster-es-http:9200]
2020-09-23 12:57:55.685 PM ERROR com.inversoft.maintenance.search.ElasticsearchMaintenanceModeSearchService - Failed to create index [fusionauth_user]. Reason + [org.elasticsearch.client.ResponseException: method [GET], host [http://10.20.30.99:9200], URI [/], status line [HTTP/1.1 401 Unauthorized]