After upgrading to Appian 25.1, the logs indicate that all services are up and running. However, HTTPS calls to port 8080 are not working.
Am seeing the following warnings in the logs:
Any help in investigate why port 8080 is not up and running would be much appreciated?
All 15 requested services are running [analytics00, analytics01, analytics02, channels, content, download-stats, execution00, execution01, execution02, forums, groups, notifications, notifications-email, portal, process-design]
0 [main] INFO com.appian.data.server.Watchdog - Data Server is starting using the [ALL_COMPONENTS_MODE] startup mode.18 [main] INFO com.appian.data.TopologyFactory - Loading topology /usr/local/appian/data-server/conf/appian-topology.xml
**************************************************************************************
Regenerating the server certificate.warning: ignoring JAVA_HOME=/usr/local/appian/java; using ES_JAVA_HOMEThis tool assists you in the generation of X.509 certificates and certificatesigning requests for use with SSL/TLS in the Elastic stack.
The 'cert' mode generates X.509 certificate and private keys. * By default, this generates a single certificate and key for us **************************************************************************************
[2025-05-13T21:09:15,773][INFO ][org.elasticsearch.node.Node] [localhost] Default Locale [en_US][2025-05-13T21:09:17,337][WARN ][com.amazonaws.auth.profile.internal.BasicProfileConfigFileLoader] [localhost] Unable to load config file nulljava.security.AccessControlException: access denied ("java.io.FilePermission" "/export/home/.aws/config" "read") at java.security.AccessControlContext.checkPermission(AccessControlContext.java:485) ~[?:?] at java.security.AccessController.checkPermission(AccessController.java:1068) ~[?:?] at java.lang.SecurityManager.checkPermission(SecurityManager.java:416) ~[?:?] at java.lang.SecurityManager.checkRead(SecurityManager.java:756) ~[?:?] at java.io.File.exists(File.java:829) ~[?:?] at com.amazonaws.profile.path.config.SharedConfigDefaultLocationProvider.getLocation(Shared
Discussion posts and replies are publicly visible
Have you checked if the search server and Tomcat are also running?
Could you check whether there’s something already running on that port?