Question

Error with Teamcenter Login: Failed to get an HTTP response.

0

Hi, I'm getting this error whenever I try to login to a newly configured Teamcenter instance: Here is my Teamcenter configuration: Here is the call that is being sent out: Could there be a configuration for using HTTPS in the Teamcenter Connector?

asked 2025-06-03

Tyron Corpuz

3 answers

Vishwa N · Answer 1 · 2025-06-04

Hi Tyron Corpuz,

You need to make sure few things. I observed from error messege your mendix application unable find teamcenter in the given URL.

check,

1. Your teamcenter server is up.

2. Try to access your AWC in your browser, to ensure that you have access from your IP.

Thanks.

Colin Marshall · Answer 2 · 2025-06-04

If you're using https you need to add the certificate from the server to Studio Pro in App Settings

SASIDARAN S · Answer 3 · 2025-06-05

Hi Tyron Corpuz,

It looks like the issue might be related to several possible areas. First, please verify if the Teamcenter server is up and running by accessing the URL https://zp-amcap-sweb01.hoplite.local:7001/tc using a browser, Postman, or curl. If the server is down, restart the Teamcenter service. Next, confirm that the endpoint in your Mendix configuration matches the actual Teamcenter URL and port; if there's a mismatch, update the connection settings in your Mendix app or within the TcConnector module. Additionally, ensure your Mendix server can resolve and reach zp-amcap-sweb01.hoplite.local. If not, you may need to add the necessary DNS entries or modify the hosts file (on Linux: /etc/hosts, on Windows: C:\Windows\System32\drivers\etc\hosts) or contact your IT/network administrator. Also, check if a firewall or proxy is blocking port 7001 or HTTPS traffic and, if so, configure the necessary rules to allow communication between Mendix and Teamcenter. Lastly, since HTTPS is being used, there could be an SSL certificate validation issue. In that case, either import the Teamcenter SSL certificate into the Mendix truststore or, for development purposes only, disable strict SSL checks (not recommended for production environments). I hope this helps in identifying and resolving the issue.

Thanks.