SSL publishing: filename vs. CMS link

I’m having trouble with publishing using SSL over port 9443,and one of my symptoms is that when I look at a publication log, the filename (on the left) starts with a domain name like https://website.com:9443/Site_Home/index.html while the CMS link (on the right) starts with an IP address like http://156.92.12.120:9992/Rhythmyx/assembler/render etc.

So I get error messages, when I publish, that http://156.92.12.120:9992/ doesn’t match the name in my certificate, which is https://website.com. How do I make the URLs match the certificate name? I don’t think I’m using the IP address in any of my settings, just my domain name.

Actually, the error message is slightly different.

com.percussion.publisher.client.PSContentFetchException: Name in certificate cms.mysite.com' does not match host name156.16.25.142’

Just before that, it says it is
Getting content item from URL : https://165.91.22.140:9443/Rhythmyx/assembler/render?sys_revision=9&sys_siteid=325
&sys_template=599&sys_itemfilter=public&sys_contentid=730&sys_folderid=726
&sys_context=301&sys_publish=publish

From the URL, I thought I was publishing happily using SSL, until I added the sslport configuration parameter of 9443, and I began getting these error messages.

Michael,

Can you post the stack trace from the Rhythmyx server console? The behavior you are reporting resembles a bug that was logged for Publishing over SSL in Version 6.0, but I’d like to compare the stack trace.

RLJII

Does this help?

com.percussion.publisher.client.PSContentFetchException: Name in certificate `tamuweb-6.tamu.edu' does not match host name `165.91.22.140'
     at com.percussion.publisher.PSUtils.fetchContent(Unknown Source)
     at com.percussion.publisher.client.PSContentItem.publish(Unknown Source)
     at com.percussion.publisher.client.PSContentItem.process(Unknown Source)
     at com.percussion.publisher.client.PSContentPublisher.process(Unknown Source)
     at com.percussion.publisher.client.PSContentPublisher.execute(Unknown Source)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
     at java.lang.reflect.Method.invoke(Unknown Source)
     at org.apache.soap.server.RPCRouter.invoke(RPCRouter.java:146)
     at org.apache.soap.providers.RPCJavaProvider.invoke(RPCJavaProvider.java:129)
     at org.apache.soap.server.http.RPCRouterServlet.doPost(RPCRouterServlet.java:354)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
     at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:81)
     at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
     at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
     at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
     at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
     at org.jboss.web.tomcat.security.CustomPrincipalValve.invoke(CustomPrincipalValve.java:39)
     at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:159)
     at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:59)
     at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
     at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
     at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
     at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
     at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856)
     at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:744)
     at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
     at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80)
     at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684)
     at java.lang.Thread.run(Unknown Source)

Michael,

Yes, it does provide more information. At this point, Tech Support can more effectively provide assistance with resolving this issue.

RLJII