The error messages you're encountering indicate that there are connectivity issues between the client (possibly a web browser or an application) and the server (hosted at dev-joget.XXX.net). 

Possible causes and solutions:

1. Network Issues: It seems there might be network connectivity issues between the client and the server. This could be due to firewall rules, network congestion, DNS resolution problems, or other network-related issues. Check if you can ping the server's IP address (100.67.119.128 or 100.67.68.84) from the client to ensure basic network connectivity.
2. Server Overload: The upstream server (100.67.1.182) might be overloaded or experiencing high traffic, resulting in delayed responses. Check the server's resource utilization (CPU, memory, etc.) and ensure that it has sufficient capacity to handle incoming requests.
3. Firewall or Security Settings: Firewalls, security groups, or access control lists could be blocking the incoming requests. Make sure that the necessary ports (443 for HTTPS) are open and accessible.
4. Proxy Configuration: If there's a proxy server or load balancer in front of the application server, ensure that it's properly configured and forwarding requests to the correct backend server.
5. Server Software Configuration: Review the configuration of the Java application server and Nginx to ensure they are set up correctly. Check for any misconfigurations that might be causing the timeouts.
6. DNS Resolution: Ensure that DNS resolution is working properly for the domain dev-joget.XXX.net. Incorrect DNS settings could lead to connection timeouts.
7. SSL/TLS Issues: If HTTPS is being used, there could be SSL/TLS certificate issues that are causing the connection to fail. Ensure that the server's SSL certificate is valid and properly configured.
8. Server Logs: Check the logs of both the Java application server and Nginx for more detailed error messages. These logs might provide more context about the nature of the issue.

Diagnosing and resolving network and server issues like these often involves a process of elimination. You might need to investigate each possible cause and solution step by step until you identify the root cause of the connectivity problem.

Thanks for the attempt, Matthew. The fact Joget works fine when using port forwarding instead of ingress eliminates almost all the items in your list. I checked the others and they are not the problem. I'll keep looking.