[GH-ISSUE #285] Goproxy stops working because of update check fail

kerem commented

2026-02-27 23:15:56 +03:00

Owner

Originally created by @xtrime-ru on GitHub (Jun 23, 2019).
Original GitHub issue: https://github.com/snail007/goproxy/issues/285

Goproxy stops working because of update check fail.

Expected Behavior

do not exit on update check fail

Current Behavior

Goproxy stops working because of update check fail.

Possible Solution

Do not exit from goproxy on update check fail. Reduce update checks.

Steps to Reproduce

Run old version of goproxy with supervisor or --forever mode.

Context (Environment)

proxy version is : 7.4, 7.5
full command is : proxy socks -p ":12246" -F "/etc/proxy/auth-file.txt"
system is : ubuntu 18.04 x64
full log is:

root@static:~# proxy socks -p ":12246" -F "/etc/proxy/auth-file.txt"
proxy free version 7.5  by snail , email : arraykeys@gmail.com
2019/06/23 23:01:16 auth data added from file 2 , total:2
2019/06/23 23:01:16 tcp socks proxy on [::]:12246
...
2019/06/23 23:01:22 check update fail, <!DOCTYPE html>
<!--[if lt IE 7]> <html class="no-js ie6 oldie" lang="en-US"> <![endif]-->
<!--[if IE 7]>    <html class="no-js ie7 oldie" lang="en-US"> <![endif]-->
<!--[if IE 8]>    <html class="no-js ie8 oldie" lang="en-US"> <![endif]-->
<!--[if gt IE 8]><!--> <html class="no-js" lang="en-US"> <!--<![endif]-->
<head>
<title>Access denied | lic00.host900.com used Cloudflare to restrict access</title>
<meta charset="UTF-8" />
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<meta http-equiv="X-UA-Compatible" content="IE=Edge,chrome=1" />
<meta name="robots" content="noindex, nofollow" />
<meta name="viewport" content="width=device-width,initial-scale=1,maximum-scale=1" />
<link rel="stylesheet" id="cf_styles-css" href="/cdn-cgi/styles/cf.errors.css" type="text/css" media="screen,projection" />
<!--[if lt IE 9]><link rel="stylesheet" id='cf_styles-ie-css' href="/cdn-cgi/styles/cf.errors.ie.css" type="text/css" media="screen,projection" /><![endif]-->
<style type="text/css">body{margin:0;padding:0}</style>


<!--[if gte IE 10]><!--><script type="text/javascript" src="/cdn-cgi/scripts/zepto.min.js"></script><!--<![endif]-->
<!--[if gte IE 10]><!--><script type="text/javascript" src="/cdn-cgi/scripts/cf.common.js"></script><!--<![endif]-->



</head>
<body>
  <div id="cf-wrapper">
    <div class="cf-alert cf-alert-error cf-cookie-error" id="cookie-alert" data-translate="enable_cookies">Please enable cookies.</div>
    <div id="cf-error-details" class="cf-error-details-wrapper">
      <div class="cf-wrapper cf-header cf-error-overview">
        <h1>
          <span class="cf-error-type" data-translate="error">Error</span>
          <span class="cf-error-code">1006</span>
          <small class="heading-ray-id">Ray ID: 4eb90db1dac62334 &bull; 2019-06-23 20:01:22 UTC</small>
        </h1>
        <h2 class="cf-subheadline">Access denied</h2>
      </div><!-- /.header -->

      <section></section><!-- spacer -->

      <div class="cf-section cf-wrapper">
        <div class="cf-columns two">
          <div class="cf-column">
            <h2 data-translate="what_happened">What happened?</h2>
            <p>The owner of this website (lic00.host900.com) has banned your IP address (xxx.xxx.xx.xx).</p>
          </div>

          
        </div>
      </div><!-- /.section -->

      <div class="cf-error-footer cf-wrapper">
  <p>
    <span class="cf-footer-item">Cloudflare Ray ID: <strong>4eb90db1dac62334</strong></span>
    <span class="cf-footer-separator">&bull;</span>
    <span class="cf-footer-item"><span>Your IP</span>: xxx.xxx.xx.xx</span>
    <span class="cf-footer-separator">&bull;</span>
    <span class="cf-footer-item"><span>Performance &amp; security by</span> <a href="https://www.cloudflare.com/5xx-error-landing?utm_source=error_footer" id="brand_link" target="_blank">Cloudflare</a></span>
    
  </p>
</div><!-- /.error-footer -->


    </div><!-- /#cf-error-details -->
  </div><!-- /#cf-wrapper -->

  <script type="text/javascript">
  window._cf_translation = {};
  
  
</script>

</body>
</html>

Detailed Description

Im running goproxy with supervisor and it restart it on fail. Probably my ip was banned on cloudflare because too many connections because of restarts of goproxy.

Originally created by @xtrime-ru on GitHub (Jun 23, 2019). Original GitHub issue: https://github.com/snail007/goproxy/issues/285 Goproxy stops working because of update check fail. ## Expected Behavior do not exit on update check fail ## Current Behavior Goproxy stops working because of update check fail. ## Possible Solution Do not exit from goproxy on update check fail. Reduce update checks. ## Steps to Reproduce Run old version of goproxy with supervisor or --forever mode. ## Context (Environment)   1. proxy version is : 7.4, 7.5 1. full command is : proxy socks -p ":12246" -F "/etc/proxy/auth-file.txt" 1. system is : ubuntu 18.04 x64 1. full log is: ``` root@static:~# proxy socks -p ":12246" -F "/etc/proxy/auth-file.txt" proxy free version 7.5 by snail , email : arraykeys@gmail.com 2019/06/23 23:01:16 auth data added from file 2 , total:2 2019/06/23 23:01:16 tcp socks proxy on [::]:12246 ... 2019/06/23 23:01:22 check update fail, <!DOCTYPE html>     <html class="no-js" lang="en-US">  <head> <title>Access denied | lic00.host900.com used Cloudflare to restrict access</title> <meta charset="UTF-8" /> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /> <meta http-equiv="X-UA-Compatible" content="IE=Edge,chrome=1" /> <meta name="robots" content="noindex, nofollow" /> <meta name="viewport" content="width=device-width,initial-scale=1,maximum-scale=1" /> <link rel="stylesheet" id="cf_styles-css" href="/cdn-cgi/styles/cf.errors.css" type="text/css" media="screen,projection" />  <style type="text/css">body{margin:0;padding:0}</style> <script type="text/javascript" src="/cdn-cgi/scripts/zepto.min.js"></script> <script type="text/javascript" src="/cdn-cgi/scripts/cf.common.js"></script> </head> <body> <div id="cf-wrapper"> <div class="cf-alert cf-alert-error cf-cookie-error" id="cookie-alert" data-translate="enable_cookies">Please enable cookies.</div> <div id="cf-error-details" class="cf-error-details-wrapper"> <div class="cf-wrapper cf-header cf-error-overview"> <h1> <span class="cf-error-type" data-translate="error">Error</span> <span class="cf-error-code">1006</span> <small class="heading-ray-id">Ray ID: 4eb90db1dac62334 • 2019-06-23 20:01:22 UTC</small> </h1> <h2 class="cf-subheadline">Access denied</h2> </div> <section></section> <div class="cf-section cf-wrapper"> <div class="cf-columns two"> <div class="cf-column"> <h2 data-translate="what_happened">What happened?</h2> <p>The owner of this website (lic00.host900.com) has banned your IP address (xxx.xxx.xx.xx).</p> </div> </div> </div> <div class="cf-error-footer cf-wrapper"> <p> <span class="cf-footer-item">Cloudflare Ray ID: <strong>4eb90db1dac62334</strong></span> <span class="cf-footer-separator">•</span> <span class="cf-footer-item"><span>Your IP</span>: xxx.xxx.xx.xx</span> <span class="cf-footer-separator">•</span> <span class="cf-footer-item"><span>Performance & security by</span> <a href="https://www.cloudflare.com/5xx-error-landing?utm_source=error_footer" id="brand_link" target="_blank">Cloudflare</a></span> </p> </div> </div> </div> <script type="text/javascript"> window._cf_translation = {}; </script> </body> </html> ``` ## Detailed Description Im running goproxy with supervisor and it restart it on fail. Probably my ip was banned on cloudflare because too many connections because of restarts of goproxy.

kerem closed this issue

2026-02-27 23:15:56 +03:00

kerem commented

2026-02-27 23:15:56 +03:00

Author

Owner

@snail007 commented on GitHub (Jun 24, 2019):

your IP have behavior of attacking , was blocked.

@snail007 commented on GitHub (Jun 24, 2019): your IP have behavior of attacking , was blocked.

kerem commented

2026-02-27 23:15:56 +03:00

Author

Owner

@gemingguo commented on GitHub (Jun 24, 2019):

I also have the problem yesterday ,the proxy program has run on aliyun server for 1 month,and yesterday the program was broken down suddenly,when i open debug mode,it show the error: update check fail, i don't know how to resolve it,and i was very upset, why does it must update?

@gemingguo commented on GitHub (Jun 24, 2019): I also have the problem yesterday ,the proxy program has run on aliyun server for 1 month,and yesterday the program was broken down suddenly,when i open debug mode,it show the error: update check fail, i don't know how to resolve it,and i was very upset, why does it must update?

kerem commented

2026-02-27 23:15:56 +03:00

Author

Owner

@fox0014 commented on GitHub (Jun 24, 2019):

your IP have behavior of attacking , was blocked.

how can fix?

@fox0014 commented on GitHub (Jun 24, 2019): > your IP have behavior of attacking , was blocked. how can fix?

kerem commented

2026-02-27 23:15:56 +03:00

Author

Owner

@healthly commented on GitHub (Jun 24, 2019):

the same problem

@healthly commented on GitHub (Jun 24, 2019): the same problem

kerem commented

2026-02-27 23:15:57 +03:00

Author

Owner

@snail007 commented on GitHub (Jun 24, 2019):

your IP have behavior of attacking , was blocked.

how can fix?

i will unban your ip.

@snail007 commented on GitHub (Jun 24, 2019): > > your IP have behavior of attacking , was blocked. > > how can fix? i will unban your ip.

kerem commented

2026-02-27 23:15:57 +03:00

Author

Owner

@xtrime-ru commented on GitHub (Jun 24, 2019):

your IP have behavior of attacking , was blocked.

if proxy in --forever mode, or monitored and restarted by supervisor you will get this "attack" after every update :)

This is how my log looks like:

proxy free version 7.4  by snail , email : arraykeys@gmail.com
2019/06/23 01:34:44 auth data added from file 2 , total:2
2019/06/23 01:34:44 tcp socks proxy on [::]:12246
2019/06/23 01:34:49 check update fail, 
proxy free version 7.4  by snail , email : arraykeys@gmail.com
2019/06/23 01:34:50 auth data added from file 2 , total:2
2019/06/23 01:34:50 tcp socks proxy on [::]:12246
2019/06/23 01:34:56 check update fail, 
proxy free version 7.4  by snail , email : arraykeys@gmail.com
2019/06/23 01:34:57 auth data added from file 2 , total:2
2019/06/23 01:34:57 tcp socks proxy on [::]:12246
2019/06/23 01:35:02 check update fail, 
proxy free version 7.4  by snail , email : arraykeys@gmail.com
2019/06/23 01:35:04 auth data added from file 2 , total:2
2019/06/23 01:35:04 tcp socks proxy on [::]:12246
2019/06/23 01:35:09 check update fail, 
proxy free version 7.4  by snail , email : arraykeys@gmail.com
2019/06/23 01:35:10 auth data added from file 2 , total:2
2019/06/23 01:35:10 tcp socks proxy on [::]:12246
2019/06/23 01:35:15 check update fail, 
proxy free version 7.4  by snail , email : arraykeys@gmail.com
2019/06/23 01:35:16 auth data added from file 2 , total:2
2019/06/23 01:35:16 tcp socks proxy on [::]:12246
2019/06/23 01:35:22 check update fail, 
proxy free version 7.4  by snail , email : arraykeys@gmail.com
2019/06/23 01:35:23 auth data added from file 2 , total:2
2019/06/23 01:35:23 tcp socks proxy on [::]:12246
2019/06/23 01:35:28 check update fail, 
proxy free version 7.4  by snail , email : arraykeys@gmail.com
2019/06/23 01:35:29 auth data added from file 2 , total:2
2019/06/23 01:35:29 tcp socks proxy on [::]:12246
2019/06/23 01:35:34 check update fail,

@xtrime-ru commented on GitHub (Jun 24, 2019): > your IP have behavior of attacking , was blocked. if proxy in --forever mode, or monitored and restarted by supervisor you will get this "attack" after every update :) This is how my log looks like: ``` proxy free version 7.4 by snail , email : arraykeys@gmail.com 2019/06/23 01:34:44 auth data added from file 2 , total:2 2019/06/23 01:34:44 tcp socks proxy on [::]:12246 2019/06/23 01:34:49 check update fail, proxy free version 7.4 by snail , email : arraykeys@gmail.com 2019/06/23 01:34:50 auth data added from file 2 , total:2 2019/06/23 01:34:50 tcp socks proxy on [::]:12246 2019/06/23 01:34:56 check update fail, proxy free version 7.4 by snail , email : arraykeys@gmail.com 2019/06/23 01:34:57 auth data added from file 2 , total:2 2019/06/23 01:34:57 tcp socks proxy on [::]:12246 2019/06/23 01:35:02 check update fail, proxy free version 7.4 by snail , email : arraykeys@gmail.com 2019/06/23 01:35:04 auth data added from file 2 , total:2 2019/06/23 01:35:04 tcp socks proxy on [::]:12246 2019/06/23 01:35:09 check update fail, proxy free version 7.4 by snail , email : arraykeys@gmail.com 2019/06/23 01:35:10 auth data added from file 2 , total:2 2019/06/23 01:35:10 tcp socks proxy on [::]:12246 2019/06/23 01:35:15 check update fail, proxy free version 7.4 by snail , email : arraykeys@gmail.com 2019/06/23 01:35:16 auth data added from file 2 , total:2 2019/06/23 01:35:16 tcp socks proxy on [::]:12246 2019/06/23 01:35:22 check update fail, proxy free version 7.4 by snail , email : arraykeys@gmail.com 2019/06/23 01:35:23 auth data added from file 2 , total:2 2019/06/23 01:35:23 tcp socks proxy on [::]:12246 2019/06/23 01:35:28 check update fail, proxy free version 7.4 by snail , email : arraykeys@gmail.com 2019/06/23 01:35:29 auth data added from file 2 , total:2 2019/06/23 01:35:29 tcp socks proxy on [::]:12246 2019/06/23 01:35:34 check update fail, ```

kerem commented

2026-02-27 23:15:57 +03:00

Author

Owner

@xtrime-ru commented on GitHub (Jun 24, 2019):

i will unban your ip.

Thanks.

how can fix?

I updated goproxy to latest version, then added this line to my /etc/hosts:

127.0.0.1 lic00.host900.com

This will disable requests to update server and your ip will be unbaned in a day. But goproxy still will restart every few seconds. After ip is unbanned - disable this line and goproxy will work untill next update :)

@xtrime-ru commented on GitHub (Jun 24, 2019): > i will unban your ip. Thanks. > how can fix? I updated goproxy to latest version, then added this line to my /etc/hosts: ``` 127.0.0.1 lic00.host900.com ``` This will disable requests to update server and your ip will be unbaned in a day. But goproxy still will restart every few seconds. After ip is unbanned - disable this line and goproxy will work untill next update :)

kerem commented

2026-02-27 23:15:57 +03:00

Author

Owner

@snail007 commented on GitHub (Jun 24, 2019):

i will unban your ip.

Thanks.

how can fix?

I updated goproxy to latest version, then added this line to my /etc/hosts:
127.0.0.1 lic00.host900.com
This will disable requests to update server and your ip will be unbaned in a day. But goproxy still will restart every few seconds. After ip is unbanned - disable this line and goproxy will work untill next update :)

that's right,you are smart.
i have already updated service of checker, it's will work well with --forever.

@snail007 commented on GitHub (Jun 24, 2019): > > i will unban your ip. > > Thanks. > > > how can fix? > > I updated goproxy to latest version, then added this line to my /etc/hosts: > > ``` > 127.0.0.1 lic00.host900.com > ``` > > This will disable requests to update server and your ip will be unbaned in a day. But goproxy still will restart every few seconds. After ip is unbanned - disable this line and goproxy will work untill next update :) that's right,you are smart. i have already updated service of checker, it's will work well with --forever.

kerem commented

2026-02-27 23:15:57 +03:00

Author

Owner

@oneryx commented on GitHub (Jun 25, 2019):

Same issue with v7.6, IP 203.211.125.64.
It would be better if it could run without update check.

@oneryx commented on GitHub (Jun 25, 2019): Same issue with v7.6, IP 203.211.125.64. It would be better if it could run without update check.

kerem commented

2026-02-27 23:15:57 +03:00

Author

Owner

@snail007 commented on GitHub (Jun 25, 2019):

https://github.com/snail007/goproxy/wiki/%E6%8F%90%E7%A4%BA%E8%AE%BF%E9%97%AE%E6%9B%B4%E6%96%B0%E5%A4%B1%E8%B4%A5%EF%BC%9F

@snail007 commented on GitHub (Jun 25, 2019): https://github.com/snail007/goproxy/wiki/%E6%8F%90%E7%A4%BA%E8%AE%BF%E9%97%AE%E6%9B%B4%E6%96%B0%E5%A4%B1%E8%B4%A5%EF%BC%9F

kerem commented

2026-02-27 23:15:57 +03:00

Author

Owner

@oneryx commented on GitHub (Jun 25, 2019):

https://github.com/snail007/goproxy/wiki/%E6%8F%90%E7%A4%BA%E8%AE%BF%E9%97%AE%E6%9B%B4%E6%96%B0%E5%A4%B1%E8%B4%A5%EF%BC%9F

这个是解决不能连外网的问题吧？现在的问题是可以联网但是不知道为什么IP被列入黑名单，进入了黑名单就意味着不能使用了，必须要等人工解锁。

@oneryx commented on GitHub (Jun 25, 2019): > https://github.com/snail007/goproxy/wiki/%E6%8F%90%E7%A4%BA%E8%AE%BF%E9%97%AE%E6%9B%B4%E6%96%B0%E5%A4%B1%E8%B4%A5%EF%BC%9F 这个是解决不能连外网的问题吧？现在的问题是可以联网但是不知道为什么IP被列入黑名单，进入了黑名单就意味着不能使用了，必须要等人工解锁。

kerem commented

2026-02-27 23:15:57 +03:00

Author

Owner

@snail007 commented on GitHub (Jun 25, 2019):

203.211.125.64

unbanned

@snail007 commented on GitHub (Jun 25, 2019): > 203.211.125.64 unbanned

kerem commented

2026-02-27 23:15:57 +03:00

Author

Owner

@snail007 commented on GitHub (Jun 25, 2019):

#286

@snail007 commented on GitHub (Jun 25, 2019): #286

Rows
Columns

[GH-ISSUE #285] Goproxy stops working because of update check fail #203

Expected Behavior

Current Behavior

Possible Solution

Steps to Reproduce

Context (Environment)

Detailed Description