Proxy settings

If your project can communicate with other stations on your local network (for example, PLCs, thin clients, external databases) but it cannot access the Internet, you might need to configure proxy settings on the computer or device that hosts the project runtime.

Some features of the project runtime use the command-line interface (CLI) to activate third-party tools, and some of those tools connect to other services over the Internet, so the CLI itself often needs to be able to access the Internet. If your local network uses a network gateway or proxy server to control access, however, you might need to configure the proxy settings for the CLI — specifically, you need to set environment variables for the protocols used by the CLI to access the Internet.

Please note the CLI has its own proxy settings separate from other applications on the same computer. Even if you previously configured the proxy settings for the web browser, for example, you still need to configure the proxy settings for the CLI.

Of course, you should do this only if your project actually needs to access the Internet — in other words, if you have developed your project to take advantage of those features that access the Internet but it does not behave as expected during project run time. Otherwise, you should leave the proxy settings unchanged in order to maintain network security and privacy.

For more information, consult your network administrator.