On Tue, Jul 12, 2016 at 8:49 AM, Sean Son <linuxmailinglistsem...@gmail.com> wrote:
> > > On Mon, Jul 11, 2016 at 6:25 PM, Ognjen Blagojevic < > ognjen.d.blagoje...@gmail.com> wrote: > >> On 11.7.2016 16:29, Sean Son wrote: >> >>> Here is the certificate path: >>> >>> - Go Daddy Root Certificate Authority - G2 >>> - Go Daddy Secure Certificate Authority - G2 >>> - *.example.com <http://example.com> >>> >>> >> That looks Ok. >> >> Did you, perhaps, tried to access server on subdomain of example.com? >> Wildcard certificate "*.example.com" is valid for "www.example.com", but >> not for "www.department.example.com". >> >> -Ognjen >> >> >> > Hello thank you for your response. I am currently only accessing the > server using IP address only. We do not have a DNS record set up for the > server as of yet. It will be something like webapp.example.com > > > Thanks > > > Are there any logs on the tomcat server that I should check in order to fix this SSL issue? or is this strictly a certificate related issue?
