Addressing Proxy Server Issues
If your company uses an HTTP proxy server to control internet access, the QNX Software Center can usually detect it automatically and communicate with the necessary QNX servers upstream of the proxy server. Sometimes, though, you have to manually configure the proxy server or provide proxy credentials. The procedures given here help you address these and other connectivity problems.
Communication with server processes
- myQNX server, hosted on www.qnx.com
- The QNX Software Center queries this server to discover and download available packages.
- QNX license server, hosted on www.qnx.com
- This server is queried to discover any licenses the user might have, and to remotely activate or deactivate those licenses.
- Content management server(s)
- The actual package download occurs via content management server(s). Depending on the location,
this may require additional whitelisting. The best way to identify the specific download server
is to test the connection, as explained in
Manually configuring proxy settings
. If the connection fails, the server name is displayed. - Floating license server installed in end-user's local network (optional)
- This server is used only by customers who have floating licenses.
All communications with the myQNX server and the QNX license server occur over HTTP and can be mediated through an HTTP proxy server. The floating license server, however, uses a proprietary protocol that isn't affected by proxy servers—it works only over direct connections.
Dealing with bad connection attempts to myQNX server
- Make sure your workstation is connected to the internet.
- Try accessing www.qnx.com from your workstation web browser. If that fails, ask your IT department to give you access to our website, either directly or through a proxy server.
- If you're using a macOS host, configure the QNX Software Center to use the same proxy settings as your web
browser, as explained in
Manually configuring proxy settings
. - If the QNX Software Center prompts you for proxy server credentials, follow the steps in
Entering proxy credentials
.
There's an issue in version 1.0 that prevents you from using uppercase characters in your login credentials.
So, always enter your login name in all lowercase characters; for instance, use myusername@mycompany.com
,
not MyUserName@mycompany.com
.
Where to find the log file with networking information
The QNX Software Center creates a log file that QNX support staff can use to diagnose networking issues. You can find this file at ~/.qnx/swupdate/.metadata/.log.