MID Server Proxy Details
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-11-2023 03:35 AM
Hi Community
We've observed a number of our MID Servers not auto upgrading successfully. This might not be the issue but I'm a bit curious why some of our configs are different.
On the MIDs that fail to auto upgrade, in the config the Proxy password is encrypted. On the MIDs that auto upgrade successfully the password is not encrypted. As far as I know, all the MIDs have been configured the same way, some slightly older than others.
Has anyone come across this?
Thanks
Marvin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-11-2023 08:21 AM
Please check The MID Server host computer must have access to the ServiceNow download site at install.service-now.com to upgrade automatically. Also Please check it can reach through the proxy as well
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-12-2023 04:43 PM
This truly when setting the password from the MID config file encrypt was set to false; and saved and started MID Services.
If you open the other config file MID server you find the encrypt ='true'.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-11-2024 12:17 AM
We've had a similar issue with our MID Servers not auto upgrading, and we noticed some configuration differences as well. For us, the proxy password being encrypted or not didn't seem to be the root cause, but it definitely raised some eyebrows.
A few things you might want to check:
Ensure all your MID Servers are running the same version.
Double-check the permissions on the directories where the MID Servers are installed.
Verify that the network connectivity is consistent for all servers.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-17-2024 05:04 AM
We've had a similar issue with our MID Servers not auto upgrading, and we noticed some configuration differences as well. For us, the proxy password being encrypted or not didn't seem to be the root cause, but it definitely raised some eyebrows.
A few things you might want to check:
Ensure all your MID Servers are running the same version.
Double-check the permissions on the directories where the MID Servers are installed.
Verify that the network connectivity is consistent for all servers.
One thing that also made a big difference for us was using rotating datacenter proxies. I was skeptical at first, but they really helped us streamline our network traffic and maintain consistent performance across all our servers. It might be worth looking into if you haven't already.
Anyway, I hope this helps.
