Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

Hi! First time deploying to DigitalOcean and think I’m almost there. Can see either my backend or frontend. If I only run the server (https://outdoors.rest:8080/api/membership) I can see my membership JSON file with the following index.ts file.
import express from 'express'
import userRoutes from './routes/user-routes'
import membershipRoutes from './routes/membership-routes'
import memberPlanRoutes from './routes/plan-routes'
import passwordRoutes from './routes/password-routes'
import memberExtendRoutes from './routes/extend-routes'
import bodyParser from 'body-parser'
import mongoose from 'mongoose'
import dotenv from 'dotenv'
import cors from 'cors'
import path from 'path'
const app = express()
dotenv.config()
app.use(express.urlencoded({ limit: '50mb', extended: true }))
app.use(cors())
app.enable('trust proxy')
app.use((req, res, next) => {
res.setHeader('Access-Control-Allow-Origin', '*')
res.setHeader(
'Access-Control-Allow-Headers',
'Origin, X-Requested-With, Content-Type, Accept, Authorization'
)
res.setHeader('Access-Control-Allow-Methods', 'GET, POST, PATCH, DELETE')
next()
})
app.use('/api/membership/webhook', bodyParser.raw({ type: '*/*' }))
app.use(express.json({ limit: '50mb' }))
app.use('/api/user', userRoutes)
app.use('/api/membership', membershipRoutes)
app.use('/api/plan', memberPlanRoutes)
app.use('/api/password', passwordRoutes)
app.use('/api/extend', memberExtendRoutes)
mongoose.connect(process.env.MONGODB_URL as string).then(() => {
console.log('connected to mongodb')
})
app.listen(8080, () => {
console.log(`Your server is ready on port 8080!`)
})
If I include the following in my index.ts file
_// app.use(express.static(path.join(__dirname, 'static')));_
_// app.get('*', (req, res) => {_
_// res.sendFile(path.resolve(__dirname, 'static', 'index.html'));_
_// });_
and run https:outdoors.rest, the frontend is connecting and running, but the backend isn’t connected, it times out. (membership info on home page)
console in dev tools says GET https://outdoors.rest:8080/api/membership net::ERR_CONNECTION_TIMED_OUT Uncaught (in promise)
My nginx setup:
server {
index index.html index.htm index.nginx-debian.html;
server_name outdoors.rest www.outdoors.rest;
location / {
proxy_pass http://localhost:8080;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection 'upgrade';
proxy_set_header Host $host;
proxy_cache_bypass $http_upgrade;
}
listen [::]:443 ssl ipv6only=on; # managed by Certbot
listen 443 ssl; # managed by Certbot
ssl_certificate /etc/letsencrypt/live/outdoors.rest/fullchain.pem; # managed by Certbot
ssl_certificate_key /etc/letsencrypt/live/outdoors.rest/privkey.pem; # managed by Certbot
include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot
}
server {
if ($host = www.outdoors.rest) {
return 301 https://$host$request_uri;
} # managed by Certbot
if ($host = outdoors.rest) {
return 301 https://$host$request_uri;
} # managed by Certbot
listen 80 default_server;
listen [::]:80 default_server;
server_name outdoors.rest www.outdoors.rest;
return 404; # managed by Certbot
}
Could someone please help and explain what I need to do in order to get the frontend connecting to the backend? Thank you!
009fd274aeae48f2bfbda6ef568676
Cloudstream Apk
032f50ee7f7d489db3b05e204fe139
032f50ee7f7d489db3b05e204fe139
Edward Sitarski
ebeecroft
dashan
34bcef38725b4e6eb5224ae028f17e
markatango
gouskova