到一定时间会被关掉，无法持续保活，不知道是Glitch的机制，还是脚本的问题

[fscarmen2]

到一定时间会被关掉，无法持续保活，不知道是Glitch的机制，还是脚本的问题

[fscarmen2]

应该是机制变了，建议你用第三方保活，如 https://uptimerobot.com/ 或者哪吒的功能，我迟点再看看保活那里如何处理。

[Jabi-james]

应该是机制变了，建议你用第三方保活，如 https://uptimerobot.com/ 或者哪吒的功能，我迟点再看看保活那里如何处理。

It is the Glitch mechanism

[fscarmen2]

我换了个保活的方法，看看效果，可以的话更新上去

[Jabi-james]

I changed the method of keeping alive, see the effect, update it if possible

Ok,, How can I update? Do the procedure all over again?

Thanks for the project ,

[fscarmen]

I changed the method of keeping alive, see the effect, update it if possible

Ok,, How can I update? Do the procedure all over again?

Thanks for the project ,

You can keep alive glitch by the service:　https://uptimerobot.com/

[Jabi-james]

I changed the method of keeping alive, see the effect, update it if possible

Ok,, How can I update? Do the procedure all over again?
Thanks for the project ,

You can keep alive glitch by the service:　https://uptimerobot.com/

Yes, I'm using this service, added the link, glitch gave me.

[fscarmen2]

The original method for keeping the app alive was effective, but it stopped working because Glitch imposed a restriction that prevented its own IP from accessing itself through the firewall. Today, it was discovered that the restriction has been lifted, so the original method is still valid.

原来的保活方法是有效的，后面没有更改相关代码而失效，原因是glitch官方作了限制，防火墙那里禁止了自己的IP访问自己，今天发现已经解除限制，所以原来的方法仍然可行，我今天再观察看看。

[Jabi-james]

prevented its own IP from accessing itself through the firewall.
they did that for v2ray services to stop them from working, yeah?
Yesterday I couldn't connect with glitch at all,, I will test it and report..

[Neomanbeta]

官方的5分钟限制依然是生效的，过了5分钟就休眠了，然后试了uptimerobot保活不行，查了一下，发现3年前就有人提到过，Glitch官方ban掉了uptimerobot等网站的保活功能（返回403），最后我是用uptime来保活的，希望大佬再看一下保活的问题。

[fscarmen2]

是的，Glitch 是 ban 了 uptimerebot 的访问，报错 Forbidden (403)，而自保活也一时可以一时不行，显示一样的错误，也是因为官方限制自己的 IP 来访问自己，同样的时间用其他的vps访问他的网址就行了。由于我有安装哪吒，直接就用哪吒这个服务了，还可以。

[Jabi-james]

Is there something specific we should do to use nezha or it ran automatically when we start the script on glitch?

[Neomanbeta]

I might be wrong but it seems by using nezha you have to deploy it on your VPS first in order to use it on Glitch. So i just made a cron on my VPS to curl my glitch url every 1 minute to keep it alive, but my argo domain still changed after around 24 hours which means the service got rebooted and i can't figure out why.

[fscarmen2]

I might be wrong but it seems by using nezha you have to deploy it on your VPS first in order to use it on Glitch. So i just made a cron on my VPS to curl my glitch url every 1 minute to keep it alive, but my argo domain still changed after around 24 hours which means the service got rebooted and i can't figure out why.

If you have a domain hosted on Cloudflare, you can use my feature net: https://fscarmen.cloudflare.now.cc/ to apply for json, fill the ARGO_AUTH and ARGO_DOMAIN variables in entrypoint.sh, so that you can use a fixed domain name.

[fscarmen2]

Is there something specific we should do to use nezha or it ran automatically when we start the script on glitch?

Nezha is a probe Repo : https://github.com/naiba/nezha . The principle is to use others vps to curl glitch every 30s or 1 min.

[Neomanbeta]

I might be wrong but it seems by using nezha you have to deploy it on your VPS first in order to use it on Glitch. So i just made a cron on my VPS to curl my glitch url every 1 minute to keep it alive, but my argo domain still changed after around 24 hours which means the service got rebooted and i can't figure out why.

If you have a domain hosted on Cloudflare, you can use my feature net: https://fscarmen.cloudflare.now.cc/ to apply for json, fill the ARGO_AUTH and ARGO_DOMAIN variables in entrypoint.sh, so that you can use a fixed domain name.

多谢，重新部署后搞定，弄的时候才发现 Argo-Xray-JS-PaaS和X-for-Glitch是不同的，我说我怎么半天都没找到那两个argo的参数。

[fscarmen2]

多谢，重新部署后搞定，弄的时候才发现 Argo-Xray-JS-PaaS和X-for-Glitch是不同的，我说我怎么半天都没找到那两个argo的参数。

感谢你的支持！

理论是要一样的，Argo-Xray-JS-PaaS 是万金油的通用版，而 X-for-Glitch 是针对 Glitch 的稍微改动。

只是前段时间我处理 VPS 用的 argo+xray 项目 ArgoX 是没有及时更新通用版本的项目，刚刚已经更新完成了。

最后大家可以通过以下功能网站，在不绑卡的情况下使用 Cloudflare 的 Zero Trust 服务：https://fscarmen.cloudflare.now.cc/

[fscarmen2]

应该是机制变了，建议你用第三方保活，如 https://uptimerobot.com/ 或者哪吒的功能，我迟点再看看保活那里如何处理。

It is the Glitch mechanism

We can keep alive easily by Nezha.

[Neomanbeta]

多谢，重新部署后搞定，弄的时候才发现 Argo-Xray-JS-PaaS和X-for-Glitch是不同的，我说我怎么半天都没找到那两个argo的参数。

感谢你的支持！

理论是要一样的，Argo-Xray-JS-PaaS 是万金油的通用版，而 X-for-Glitch 是针对 Glitch 的稍微改动。

只是前段时间我处理 VPS 用的 argo+xray 项目 ArgoX 是没有及时更新通用版本的项目，刚刚已经更新完成了。

最后大家可以通过以下功能网站，在不绑卡的情况下使用 Cloudflare 的 Zero Trust 服务：https://fscarmen.cloudflare.now.cc/

原来这是网址的作用是不用绑卡啊。。。我不知道，所以还是绑了卡，创建了通道以后，把billing里绑的卡再删掉，这么搞的。
顺便在这里说一下，我就不开新issue了，希望能把Argo-X-Container-PaaS也更新一下argo的那两个参数，因为我koyeb也想创建一个通道，谢谢。

[Jabi-james]

It should be that the mechanism has changed. It is recommended that you use a third-party keepalive, such as https://uptimerobot.com/ or Nezha’s function. I will see how to deal with keepalive later.

It is the Glitch mechanism

We can keep alive easily by Nezha.

To use nezha we need a paid VPS, right? And to use Argo tunnel we need to add credit card to Cloudflare which is not possible for Iranian people ,, there is no way to do these free?