Running version 5.0.0.1
I get the error message below when I open the application while connected to NordVPN:
ERROR We are sorry, but there was an error.
Message: Retry failed after 6 tries. Retry settings can be adjusted in ClientOptions.Retry or by configuring a custom retry policy in ClientOptions.RetryPolicy. (The requested address is not valid in its context. (homeupdater.patchmypc.com:443))
The last part of the message in parentheses repeats 5 times, and then the entire message repeats 5 times again
BTW, the dialog width seems to be based on the width of my display, which is 5120x1440, making it far too wide. On a normal-sized display the dialog might be more narrow, but the length of the message would probably make it exceptionally tall
I also got an error referring to spam filtering when I try to submit this post, so there is apparently an IP filter in place which has NordVPN on its blocklist. I tried to work around the filter by adding the PatchMyPC executables to a split tunnel rule, but the connection is still blocked, I'm guessing because the app uses .NET to create the connection and so the split-tunnel rule on the parent executable doesn't apply. I also used a dedicated IP address leased through Nord, and this is blocked as well - suggesting that all Nord (or maybe all VPN) addresses are blocked, not just addresses associated with suspicious activity.
Only fully disconnecting from the VPN allows the application to work.
Snippet of log file:
I get the error message below when I open the application while connected to NordVPN:
ERROR We are sorry, but there was an error.
Message: Retry failed after 6 tries. Retry settings can be adjusted in ClientOptions.Retry or by configuring a custom retry policy in ClientOptions.RetryPolicy. (The requested address is not valid in its context. (homeupdater.patchmypc.com:443))
The last part of the message in parentheses repeats 5 times, and then the entire message repeats 5 times again
BTW, the dialog width seems to be based on the width of my display, which is 5120x1440, making it far too wide. On a normal-sized display the dialog might be more narrow, but the length of the message would probably make it exceptionally tall
I also got an error referring to spam filtering when I try to submit this post, so there is apparently an IP filter in place which has NordVPN on its blocklist. I tried to work around the filter by adding the PatchMyPC executables to a split tunnel rule, but the connection is still blocked, I'm guessing because the app uses .NET to create the connection and so the split-tunnel rule on the parent executable doesn't apply. I also used a dedicated IP address leased through Nord, and this is blocked as well - suggesting that all Nord (or maybe all VPN) addresses are blocked, not just addresses associated with suspicious activity.
Only fully disconnecting from the VPN allows the application to work.
Snippet of log file:
Code Select
[2024-11-02 13:46:42] INFO Application launch.
[2024-11-02 13:46:42] DEBUG View MainViewModel has been loaded
[2024-11-02 13:47:08] ERROR System.AggregateException: Retry failed after 6 tries. Retry settings can be adjusted in ClientOptions.Retry or by configuring a custom retry policy in ClientOptions.RetryPolicy. (The requested address is not valid in its context. (homeupdater.patchmypc.com:443)) (The requested address is not valid in its context. (homeupdater.patchmypc.com:443)) (The requested address is not valid in its context. (homeupdater.patchmypc.com:443)) (The requested address is not valid in its context. (homeupdater.patchmypc.com:443)) (The requested address is not valid in its context. (homeupdater.patchmypc.com:443)) (The requested address is not valid in its context. (homeupdater.patchmypc.com:443))
---> Azure.RequestFailedException: The requested address is not valid in its context. (homeupdater.patchmypc.com:443)
---> System.Net.Http.HttpRequestException: The requested address is not valid in its context. (homeupdater.patchmypc.com:443)
---> System.Net.Sockets.SocketException (10049): The requested address is not valid in its context.
at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.ThrowException(SocketError error, CancellationToken cancellationToken)
at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.System.Threading.Tasks.Sources.IValueTaskSource.GetResult(Int16 token)
at System.Net.Sockets.Socket.<ConnectAsync>g__WaitForConnectWithCancellation|285_0(AwaitableSocketAsyncEventArgs saea, ValueTask connectTask, CancellationToken cancellationToken)
at System.Net.Http.HttpConnectionPool.ConnectToTcpHostAsync(String host, Int32 port, HttpRequestMessage initialRequest, Boolean async, CancellationToken cancellationToken)
--- End of inner exception stack trace ---