HTTP 502 errors when accessing certain parts of Appian

@phil Please check out this post for the similar issue - forum.appian.com/.../f-157031.

prosenjitd, thank you for the response. I removed the example custom.properties file from the home directory and verified that all port configurations were accurate. It did not resolve our issue.

Furthermore, in the post that you linked to, I noticed that they configured the server.conf.processcommon.MAX_EXEC_ENGINE_LOAD_METRIC property, which was missing from our custom.properties file, but that did not resolve our issue either.

Any other suggestions would be appreciated.

@Phil Can you please attach your Custom.properties? Please go through this Knowledge Base article as well to see if it gives you some direction.
Also, In the logs you attached, I noticed the entries confirming the deployment of the Plugins and don't see the confirmation regarding server being started successfully. Please go through the KB article and approach your issue as suggested.

KB Link - forum.appian.com/.../kb-1011.html

Thank you, I will review the KB article and troubleshoot with the suggested actions. In the meantime, I have attached the custom.properties file.

custom.properties

I followed the action steps in the article by verifying the configurations and making sure the web server was set up as expected, however, it did not resolve our issue.

The parts of our site that are not functioning and returning the 502 error are present in all browsers as well, not just in Chrome.

Thanks for your input, please let me know if you see anything within the custom.properties file that I attached that might stand out.

Ensure that this is URL that you are using to access Appian - appiandev.architechsolutions.com/*

That said, 502 errors are typically at the web server or proxy level and as such the configurations within Appian may not matter. See - www.checkupdown.com/.../E502.html

Try bypassing the webserver and access the application server directly:

1. Stop JBoss and change SERVER_AND_PORT in custom.properties to be the <JBOSS hostname>:8080
2. Start JBoss and access the reports, admin console etc. that were previously showing errors

If there are no errors then this would confirm that the problem is not within the Appian configurations

Make sure to use the URL http://<JBOSS hostname>:8080/suite/tempo etc. to hit the app server directly