cdf1815d-d3de-4820-866b-7fea03248e92

Railway itself is IPv4 only for the public domains, but I highly doubt Stripe is IPv6 only.

can you link the service in question please?

Sorry, what do you mean by service? I guess this was just my assumption since simply changing the setup made the webhooks no longer work

Okay nevermind stripe is ipv4 for sure..

If everything else has been working after the migration but this webhook, where should I start to dig? Is it possible this is a port issue?

I've been struggling with the port config trying to set this up

I had to set the custom port to 8080 since that seems to be the port NGINX is running on from what I can see in the deploy logs and only then was my app responding and working. However there's an option that would allow me to use port 9000

Though when I do, I can no longer access the public url

I figure there might be a mismatch here..?

oh my, I figured it out..

indeed it was just that

a port mismatch

the webhook url was set up to be sent to the railway default address which was still set to 80

But maybe one final clarification, what's up with that 9000 port and do I even need it? NGINX seems to start on 8080 and everything works properly through that port

> what do you mean by service?

thats php-fpm, you can think of it as the php interpreter, it runs on port 9000 and nginx makes requests to it via that port internally, but you should ignore it here, you do want port 8080 set

Alright, thanks for the info!

so to re-cap, you are all good now that the port is set to 8080

awesome. very new to this so I appreciate the help

Might want to change the title to better reflect the actual issue?

be my guest

PHP FPM Laravel Majestic Monolith Port Configuration

!s