Creo Elements/Direct - remote License Server

[lfortner]

With version 20.8 I cannot access anymore the remote license Server status using http://<Remote License Server>:17171. Logged to the server http://localhost:17171 works as expected.

Il there any workaround or some administration command to use?

[Catalina]

Hi @lfortner 

Thank you for your question! 

I’d like to recommend to bring more details and context to your initial inquiry. For example:

• When you try to access the remote license server via the browser, does it time out, or do you get a specific error message?
• Has anything changed in your environment recently — like a software update, firewall rule, or network policy — that might affect how remote access works?
• Is your goal mainly to monitor license usage remotely, or are you trying to perform some kind of admin task through the web interface?

Please add screenshot(s) to better understand what you are trying to do in your process. 

Please refer to this guideline to make your questions more likely to receive a quick and useful answer. 

This will increase your chances to receive meaningful help from other Community members. 

Here's what a good question for Creo looks like. 

Thank you for your participation and please let me know if you need further assistance! 

Best regards,

[lfortner]

I installed CED License Server on a computer A. I run Modeling on computer B.

Logged in computer A I can access the License Server summary page using http://localhost:17171.

But logged in computer B I cannot access the License Server summary page using http://A:17171,  I receive the following message :

     Creo Elements/Direct License Server Web Administration
     Web Administration are accessible only on the Server Host machine.
     Please refer Changelog section of User Guide for more details

This was possible and useful with License Server 20.7 and below.

From now, I cannot monitor licenses out of the computer where License Server 20.8 is installed.

[MartinG]

Same here.

It is noted in the changelog that in 20.8 only local access to the status page is possible.

Somewhat useless if you don't have physical access to the server - or need to vnc to the vm for that.

The reason might be this: https://www.cisa.gov/news-events/ics-advisories/icsa-24-177-02

License Server up to 20.7 was kind of vulnerable, so they just blocked external access instead of fixing things...

Regards,
Martin

[lfortner]

Very clear Martin.

Many thanks for the explanations.

We must comply with these new constraints.

Louis

[kurt65]

Hi all,

The restriction of access to the license server in version 20.8 is truly frustrating.

In most companies, CAD administrators do not have direct access to the IT infrastructure (for example, the license server itself). As a result, they are no longer able to independently check the current license usage status and would now have to involve an IT administrator every single time this information is needed.

This “feature” (simply blocking external access) in License Server 20.8 is, in my opinion, a very poor decision.

Regards,

Kurt

[kurt65]

Hi all again, 

PTC provides a workaround using Apache with HTTPS and LDAP authentication (see article CS454791):

https://www.ptc.com/en/support/article/CS454791

However, in our environment this setup was far more complex than necessary, especially since the license server status page is only needed for internal monitoring within the company network.

I implemented a much simpler solution using a basic Apache reverse proxy. The existing license port (17171) remains unchanged for CAD clients, while the status page is made available internally through another port.

Example configuration in httpd.conf:

LoadModule proxy_module modules/mod_proxy.so
LoadModule proxy_http_module modules/mod_proxy_http.so

<VirtualHost *:17172>
ProxyRequests Off
ProxyPreserveHost On

<Proxy *>
Require all granted
</Proxy>

ProxyPass / http://127.0.0.1:17171/
ProxyPassReverse / http://127.0.0.1:17171/
</VirtualHost>

This exposes the license server status page via:

http://server:17172

Advantages of this approach:

• License communication on port 17171 remains unchanged
• No HTTPS certificates required
• No LDAP configuration required
• Very small and easy-to-maintain configuration
• Suitable for internal networks where access risk is low

Perhaps this simplified approach can help others facing the same issue.

Regards,
Kurt