Not sure if it is the container or on pia's side. I downgraded to 4.2.1-1-05 but I'm still getting the errors messages you listed above. Ping: : Temporary failure in name resolution I also tried deleting the image and reinstalling the container, same issue. I would really appreciate any insight as to why the adapter has a conflict with the third-party VPN and what I may be able to do as a workaround. Google tells me that code 56 is known to occur when the network adapter has a conflict with the third-party VPN installed on your system. PIA VPN port assignment API currently down, terminating OpenVPN process to force retry for incoming port. Response code 000 from curl != 2xx, exhausted retries exiting script. This is what I am seeing at in the logs currently. However the container is still failing to start. I upgraded to the latest which fixed the "cannot allocate 4611686018427387903 bytes" issue. I tailed the containers logs and sure enough, that is what I was seeing. I noticed that my qBittorrent web UI was down so I came to this thread and saw the discussion regarding the "cannot allocate 4611686018427387903 bytes" issue.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |