ZWhat do you mean with doesn't work? Are you getting a 404 page?
Can you share the domain so we can take a look?
How are you hosting the react site?
Can you share the domain so we can take a look?
How are you hosting the react site?
NAssuming you deployed a react application you will need to configure a react router. https://hygraph.com/blog/routing-in-react
In this guide, we will learn how to perform routing in React using React router, as well as the various aspects of routing and how React router handles them.
RHi, the original message was deleted so I can't confirm if my issue is the same as the OP's, but I had a question around the (optional) path field when adding a hostname.
I'd like to have test.mydomain.com point to a self-hosted service (such as 192.168.1.10:8080, for instance), but have test.mydomain.com/admin point to the admin panel of that self-hosted service.
An example is speedtest-tracker, which has a public dashboard as well as an admin panel where I can login and make changes.
Is using the path field the best way to achieve this?
I'd like to have test.mydomain.com point to a self-hosted service (such as 192.168.1.10:8080, for instance), but have test.mydomain.com/admin point to the admin panel of that self-hosted service.
An example is speedtest-tracker, which has a public dashboard as well as an admin panel where I can login and make changes.
Is using the path field the best way to achieve this?
RMy ultimate intention is to have my "admin" flow give me access to my personal dashboard, which would have links to all the services and various statuses of each
