> did use setup.properties.last... does that mean that I do or don't need to sync certs?
Yes, you still need to sync certs and keystores by hand even in this case. Regardless of that issue you had even before you went for cluster, it still must be done to complete all steps guide requires from you.
You need to take certs and keystores from the `/etc/certs/` (within container) of the node you used as a source in first csync's run, and move to the `/etc/certs/` on the other node, over-writting its contents (better backup the whole directory first, just in case). You'll find full list of files to transfer [here](https://www.gluu.org/docs/cluster/#certificate-management), but in a nutshell it's everything with extensions .key, .csr, .crt, .jks, .pkcs12.
Don't forget to check ownership on newly transferred files, it must be `tomcat:tomcat`. Then you must update the default java keystore (within container) on the node where certificates and keystores in `/etc/certs/` got over-written - that's what that link I provided above will help you with.
Still, this bothers me:
> Basically, what I was trying to say with that was that prior to the clustering I had this same issue. Pre-clustering, if I used a Chrome incognito window it did not give me the error.
Do you mean you couldn't access web UI and saw the same error entries in `wrapper.log` too back then?