All geek questions in one place

Bots that prevent Meteor from deploying to Digital Ocean with Meteor Up

When I use Meteor Up to deploy my application to Digital Ocean Droplet, I get the following error in the logs that prevent the application from being deployed. I have the same deployment on another drop, without such a problem. According to my research on the Internet, this is a known issue caused by bots trying to make a GET request on the server, apparently trying to use the server as a proxy.

EDIT: To clarify, my application loads in the browser simply because of a previous successful deployment. This problem occurs when I want to deploy updates to an existing application.

My questions are as follows:

  • How did bots start acting on this particular cappella, and not on my other drops? I would like them not to do this in the future.
  • Do they constantly issue GET requests on the server? If not, should I be able to deploy when they don't attack?
  • Are bot actions harmful to my application and its data? If I do end up being deployed successfully, they will still attack my server, right?

  • How to fix a problem if it already exists on one of my Droplets? I tried changing my mup.json to use a different port, for example 108 instead of 80, but this does not help. No one solved the problem, according to my online research on GitHub, StackOverflow, etc.

    Error: URL must be relative URL: http://httpheader.net on the _.extend.classify page (packages / routepolicy / routepolicy.js: 103) in appUrl (packages / fast-render / lib / server / inject.js: 94) in Object.RouteController [as a descriptor] (packages / fast-render / lib / server / inject.js: 108) as follows (/ opt / musichunt / app / programs / server / npm / webapp / main / node_modules / connect / lib / proto.js: 190: 15) in Object.cookieParser [as a handle] (/ opt / musichunt / app / programs / server / npm / fast-render / main / node_modules / connect / lib / middleware / cookieParser .js: 65: 5) on the following (/opt/musichunt[107.170.235.251.06.2012/app/programs/server/npm/webapp/main/node_modules/connect/lib/proto.js:190:15) in Object.Package [as a descriptor] (packages / spiderable / spiderable.js: 126) as follows (/ opt / musichunt / app / programs / server / npm / webapp / main / node _modules / connect / lib / proto.js: 190: 15) in middleware (packages / oauth / oauth_server.js: 72) in packages / oauth / oauth _server.js: 61

0
source share
2 answers

This should not prevent your application from starting. Although this is a bug and a known bug, it only appears in the logs and does not crash or stop your Meteor application.

A bit annoying, these bots scan entire IP blocks for open proxies. They do no harm except the error in your magazines.

+3
source

As Akshat said, these bots should not be a problem. They do not clog your server. Usually ~ 50 of these proxies checks the day (what I saw).

You can check what meteor-up says in debug mode during deployment.
Instead of mup deploy do DEBUG=* mup deploy

You can also try another ip if this ip is too crowded. Finish your drop, take a picture. Pull a new drop from the snapshot. Check if it has a new IP address and just deploys to this new ip.

If you can expand the end, everything will work, destroy the old drop to save money;)

0
source

Source: https://habr.com/ru/post/1202455/

More articles:


All Articles