You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi engageub,
Currently, I tried to run Repocket with proxy, but seems there was an issue with Repocket and it continues restarting. Could you help me check? Thanks!
Hello,
Thank you for sharing the logs.
It appears that you are using the latest version of Repocket, while the client is using an older version.
Please note that the official Docker Repocket image is being used.
If there are any issues, we will need to contact the Repocket team.
Upon reviewing the tun2socks logs, there are timeouts for one of the IP addresses, which is not reachable via ping commands. There may be an issue with their server.
Other users have posted Repocket errors in the Discord channel, mentioning that one of the containers was showing the error.
The script is working as expected; the issue may lie with Repocket.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi engageub,
Currently, I tried to run Repocket with proxy, but seems there was an issue with Repocket and it continues restarting. Could you help me check? Thanks!
Repocket logs:
tun2sock logs:
*Using tun2proxy instead of tun2sock working fine
Beta Was this translation helpful? Give feedback.
All reactions