Unable to edit ENV

10 months ago

Hello πŸ‘‹πŸ»

I'm trying to edit my Filebeat configuration on my OpenSearch instance. My configuration is saved inside CONFIG environment variable and is copied when the containers starts. There are some modifications I can't save (I think it's because they are breaking the GraphQL request but I can't locate the problem).

Here is my actual configuration (working) :```yaml

filebeat.inputs:

  • type: http_endpoint enable: true listen_address: 0.0.0.0 listen_port: 8080 secret.header: FilebeatAuth secret.value: ${{AUTH_SECRET}}

output.logstash:

hosts: ['${{Logstash.RAILWAY_PRIVATE_DOMAIN}}:5044']```

And here is the new configuration I'm trying to save (yes I'm just trying to enable debug logging πŸ˜„) :```yaml

logging.level: debug

logging.to_files: true

logging.files:

path: /var/log/filebeat

name: debug

keepfiles: 7

filebeat.inputs:

  • type: http_endpoint enable: true listen_address: 0.0.0.0 listen_port: 8080 secret.header: FilebeatAuth secret.value: ${{AUTH_SECRET}}

output.logstash:

hosts: ['${{Logstash.RAILWAY_PRIVATE_DOMAIN}}:5044']```

Here is the error in the console :

https://backboard.railway.com/graphql/internal?q=stageEnvironmentChanges net::ERR_FAILED 403 (Forbidden)```

Thanks for your help πŸ™‚

7 Replies

10 months ago

188bf912-f6d5-473b-a04c-28fcc7d44154


clashing
FREE

10 months ago

Can you provide the build logs, which might have the exact info of the failure


clashing
FREE

10 months ago

Just redeploy the service, if there are no build logs

1399324675498180668


10 months ago

The problem doesn't come from my service but from Railway API itself since I can't even save the variable. This error happens when I try to save my variable


clashing
FREE

10 months ago

Do you have a volume attached to the service, which would be used to store the logs


10 months ago

Hello,

The 403 status code does not originate from our API.

Instead, this is Cloudflare blocking the request, likely detecting something it thinks is malicious in that config.

Fortunately, the solution is simple, and involves better practices: save the configuration files into a repo, and have a Dockerfile set to copy them into the image, like this:

https://github.com/railwayapp-templates/elasticsearch/blob/main/Dockerfile#L8-L14


10 months ago

Ok thanks I will take a look πŸ™‚


Welcome!

Sign in to your Railway account to join the conversation.

Loading...