.net 6
logfast
HOBBYOP

2 years ago

I can't connect to the endpoint

Closed

21 Replies

logfast
HOBBYOP

2 years ago

a680c428-40e9-4879-a647-e39781388c33,


2 years ago

going to need more information here, can't connect is a bit too vague unfortunately


logfast
HOBBYOP

2 years ago

I created a test API in dotnet 6, with the default endpoint and added cors for any origin, and I want to access the endpoint that is there when we create the API,

I tried with the domain:3000/GetWeatherForecast that was created, I tried to put the port in the variables and it doesn't work


2 years ago

the correct URL format would be https://domain.com/GetWeatherForecast


logfast
HOBBYOP

2 years ago

even with the domain generated by the site?


2 years ago

yeah substitute domain.com with the railway generated domain


logfast
HOBBYOP

2 years ago

Doesn't work


2 years ago

going to need more information here, doesn't work is a bit too vague unfortunately


logfast
HOBBYOP

2 years ago

1298694608351662213


logfast
HOBBYOP

2 years ago

1298694886257856613


2 years ago

that is a 404 page your own application is returning


logfast
HOBBYOP

2 years ago

same endpoint

1298699396459794432


2 years ago

are you sure you've pointed the domain to the correct port?


logfast
HOBBYOP

2 years ago

yes

1298704099419750430

1298704099738648606

1298704100044836867


2 years ago

the you would need to debug why your application is returning 404


logfast
HOBBYOP

2 years ago

I don't even know how to debug it, if it's literally a standard dotnet api project with cors without any restrictions


logfast
HOBBYOP

2 years ago

It magically started working


logfast
HOBBYOP

2 years ago

<:confused_nick:1265465478189416569>


logfast
HOBBYOP

2 years ago

thx u help


2 years ago

i didnt do anything lol


logfast
HOBBYOP

2 years ago

your presence counts


Welcome!

Sign in to your Railway account to join the conversation.

Loading...