You are currently reviewing an older revision of this page.
Login Page loads via https but static content does not load. Inspecting the page through a network capture reveals that static content response is coming from an undesired port.
Setting a Default Start Page on the 'User Start Pages' tab of the Admin Console yields the following error:
The URL is invalid or has an incorrect base URL. The base URL must be https://FQDN:<INCORRECT_PORT>
Logging in yields a 401 error when hitting:
https://<FQDN>/suite/tempo
JBoss or Tomcat fail to start with errors that point to data sources that do not exist in custom.properties, appian-ds.xml, nor standalone.xml/tomcatResources.xml.
A custom.properties file exists somewhere else on the server other than <APPIAN_HOME>/conf.
Apache commons-configuration PropertiesConfiguration will attempt to find a file specified by just the name with a call to ConfigurationUtils.locate() which resolves in the following order:
PropertiesConfiguration
ConfigurationUtils.locate()
<APPIAN_HOME>/conf/ is on the classpath, so Appian expects to use the custom.properties file on setep 4. However, if a custom.properties file is found before step 4, Appian will use that file rather than the expected custom.properties file in <APPIAN_HOME>/conf. Hence, if stale versions of custom.properties exist in a user's home directory and this user attempts to start the Application Server, Appian willl pick-up the wrong file and the Application Server will fail to start.
<APPIAN_HOME>/conf/
<APPIAN_HOME>/conf
Find and remove/rename any custom.properties files extraneous to the classpath.
Possibility to run grep at the user level to find all custom.properties files that exist on the server.
grep
Possibility to use Windows File Explorer to search for all custom.properties files that exist on the server.
This article applies to Appian 18.4 and earlier.