流星，mup＆amp; Cloudflare引起重定向/刷新循环

发布于 2025-01-25 04:20:50 字数 880 浏览 2 评论 0原文

我有一个已经存在了几年的流星WebApp。它并不是特别经常更新，因此该版本有点旧（Meteor 1.6.1.4），但是它在本地运行而没有问题，我目前有一个版本，它在Mongo上与Mongo的数字海洋滴没有任何问题Atlasdb和Cloudflare上的DNS。

但是，我一直在使用流星UP（MUP）工具来部署更新的问题。在我的生产服务器上，当我运行mup部署使用我的最新代码时，部署有效并成功验证，但是现在的实时站点现在可以在页面加载上循环。该页面完成了负载（包括对条纹API前端库的调用）和图像加载，并且一旦发生，同一页面就会一遍又一遍地加载。这发生在WebApp的每个页面上。控制台没有记录错误。

我几乎可以肯定这不是代码库问题，因为我在同一规格液滴上运行的同一应用程序的登台版本可以在没有问题的情况下部署到该应用程序。生产和演出之间的唯一区别是，该分期使用MUP和Production生成的Letsencrypt证书使用Cloudflare发布的证书。我不记得这是这样的原因，因为这是我上一轮故障排除的结果，这确实导致了成功的部署。当我上次设置所有内容时，带有MUP的Letsencrypt配置似乎是有问题的。无论哪种方式，都没有明显的充分理由发生此错误。

因此，我认为这个问题很可能与Cloudflare有关，但是我对什么没有太多线索。部署后，我尝试清除完整的缓存。由于我遇到不安全的错误，我无法禁用Cloudflare代理。

对于下一步，我正在考虑设置另一个舞台液滴，但是以相同的方式在前面，以查看我是否可以获得相同错误的非临界复制版本。从那里，我不确定我会做些什么来调试和修复。我还想知道，为此WebApp配置负载平衡器是否此时可能会很聪明，尽管如果在SSL传递中，我想知道它是否不会解决基本问题。这也不一定是回答这个问题，而是避免回答这个问题。我还在考虑尝试更新流星应用程序的版本，以查看是否有任何可能是问题的一部分。

有什么建议吗？

原文

I have a meteor webapp that has been around for a few years. It hasn't been updated particularly often and thus the version is little bit old (Meteor 1.6.1.4), however it runs locally without an issue and I currently have a version of it it deployed without issue on a Digital Ocean droplet with Mongo on AtlasDB and the DNS on Cloudflare.

However I've been running into an issue deploying updates with the Meteor Up (MUP) tool. On my production server when I run mup deploy with my latest code the deployment works and validates successfully, however the live site now loops on page load. The page completes the load (including a call to Stripe API front end library) and the images load and as soon as that has happened the same page is loaded again over and over. This happens on each page of the webapp. There are no errors logged in the console.

I'm almost sure this isn't a codebase issue as I have a staging version of this same app running on an identical spec droplet which I can deploy to without issue. The only difference between the production and staging is that the staging uses a LetsEncrypt cert generated by MUP and production uses a Cloudflare issued cert. I can't remember exactly the reason for this as it was the outcome of my last round of troubleshooting, which did result in a successful deployment. The LetsEncrypt configuration with MUP seemed to be problematic when I last set everything up. Either way there is no obvious good reason why this error should occur.

So I think that the issue is most likely something to do with Cloudflare, however I don't have many clues as to what. I've tried clearing the full cache after deploying. I cannot disable the Cloudflare proxy as I get unsecure error.

For my next steps I'm thinking of setting up another staging droplet but with Cloudflare in front in the same way, to see if I can get a non-critical replicable version of the same error. From there I'm not sure what I would do to debug and fix. I was also wondering if configuring a load balancer for this webapp might be smart at this moment, though if in an SSL passthrough I wonder if it would not solve the underlying issue. This would also not necessarily be answering this question but rather just avoiding it. I'm also considering trying to update the version of the Meteor app as far as I can to see if there is any chance that codebase is part of the issue.

Any suggestions?

分享到QQ

分享到微博