Instance is repeatedly getting created

Troubleshooting and help
,
1

The instance of my web services is repeatedly getting created even tho the service passed all health checks.
Here is the logs:

Instance created. Preparing to start...
Instance is starting. Propagating network configuration...
Network configuration propagated
Server running on port 3000
(node:1) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
[msa] First time signing in. Please authenticate now:
To sign in, use a web browser to open the page https://www.microsoft.com/link and use the code 3RVS3KVB or visit http://microsoft.com/link?otc=3RVS3KVB
Instance is healthy. All health checks are passing.
Instance created. Preparing to start...
[msa] Signed in with Microsoft
Instance is starting. Propagating network configuration...
Connecting to 52.169.162.14:30005 Dedicated Server (FAMILIA - Copy), version 1.21.21  (as 1.21.20)
Network configuration propagated
Server running on port 3000
(node:1) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
[msa] First time signing in. Please authenticate now:
To sign in, use a web browser to open the page https://www.microsoft.com/link and use the code CV8SS53H or visit http://microsoft.com/link?otc=CV8SS53H
Instance is healthy. All health checks are passing.
Instance is stopping
Instance stopped
2

There is an issue with your application I believe. Your health check might be successful because they rely on TCP. You could use HTTP as a protocol for the health check and it would be failing. The service responds with a 404 on your /health path.

3

You were correct! I don’t know how did I miss that.
But another problem is:
My service is just not wanting to work i’m running a simple http server that listens on 0.0.0.0:8001 and everything is configured correctly and i still get 404.
The whole code is tested on my machine and it works perfectly I really dont know what the problem is.

Here is the main code:

const { fork } = require('child_process');


const serverProcess = fork('./server.js');

const bedrock = require('bedrock-protocol');

// Some other code

And here is server.js:

const express = require('express')
const app = express()
const port = 8001

app.get('/', (req, res) => res.send('Hello World!'))

app.listen(port,"0.0.0.0", () => console.log(`Example app listening on port ${port}!`));

The error is:
internal deployment failure
Update:
The above error is gone and the health checks are passing but i still get 404 error

4

It seems fixed no? I get the “Hello World” response when I reach your service.