Question

How to set up a proxy from a droplet to an app deploy

Hello! We are using the DO apps to deploy a set of backend services and a single front end. We want to use the backend services for identity management in other micro-apps that we build, and are having a problem.

The source server is an expressjs based session management server. Within the app ecosystem it works perfectly.

However, we want to proxy from another server hosted on another droplet that is not in the ecosystem. This server is just running NGINX for hosting mostly static web files. We want to be able to set up a proxy on that server to the app to consume the services and overcome the CORS issues with consuming services from another place (really struggling to get cookies setting correctly).

However… when we proxy to the app, it just throws up a page that says “403 — cloudflare”.

Is there anything specific that we have to do to allow proxying INTO the app platform from another droplet?

Subscribe
Share

@cbaker – see my question above. I saw you answer another post about proxying, thought you might have a fast answer to this one as well.

Just to be clear, I want a URL from another droplet (www.foo.com/bar) to proxy into my app (foo.app/bar), but am getting a 403.


Submit an answer
You can type!ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Hey there!

It sounds like you may be hitting issues with CORS in App Platform. CORS would need to be configured in App Platform to allow your droplet to proxy to it. If you haven’t done so yet this guide can help you get that configured: App Platform CORS

If you are using middleware to manage CORS you would need to add the droplet there as well.

Hope it helps! Nate