Custom Domain/DNS issue - nothing in logs and appears setup correctly
brandonmchu
HOBBYOP

a year ago

Getting the following error when heading to my.sightlineapp.com. in railway the domain appears setup correctly, as it does in my dns. Nothing in logs.

Application failed to respond

This error appears to be caused by the application.

If this is your project, check out your deploy logs to see what went wrong. Refer to our docs on Fixing Common Errors for help, or reach out over our Help Station.

If you are a visitor, please contact the application owner or try again later.

Request ID:
saGnUPehT9u2neOE9IglcQ_2074704348

Solved

4 Replies

a year ago

This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.

Status changed to Open brody over 1 year ago



brandonmchu
HOBBYOP

a year ago

I've gone through that guide and still don't know what is wrong. here's my dockerfile for the react app

# Use an official Node runtime as the base image
FROM node:20-alpine

# Set the working directory in the container
WORKDIR /app

# Copy package.json and package-lock.json
COPY package*.json ./

# Install dependencies
RUN npm ci

# Copy the rest of the frontend code
COPY . .

# Define build arguments
ARG VITE_CLERK_PUBLISHABLE_KEY
ARG VITE_SUPABASE_URL
ARG VITE_SUPABASE_KEY
ARG VITE_BACKEND_STAGING_URL

# Set environment variables
ENV VITE_CLERK_PUBLISHABLE_KEY=${VITE_CLERK_PUBLISHABLE_KEY}
ENV VITE_SUPABASE_URL=${VITE_SUPABASE_URL}
ENV VITE_SUPABASE_KEY=${VITE_SUPABASE_KEY}
ENV VITE_BACKEND_STAGING_URL=${VITE_BACKEND_STAGING_URL}

# Build the app using Vite
RUN npm run build

# Install serve to run the application
RUN npm install -g serve

# Expose the port the app runs on
EXPOSE 5173

# Serve the app
CMD ["serve", "-s", "dist", "-l", "tcp://0.0.0.0:5173"]

brandonmchu
HOBBYOP

a year ago

Disregard - Just deleted the config in railway, and redid it and it worked. shrug


a year ago

The docs page did cover exactly what was wrong, but recreating the entire service is another way to solve it, so if it works for you then that's good!


Status changed to Solved brody over 1 year ago


Loading...