a year ago
Tried to deploy with changing the docker image to the latest but it failed with following deploy log:
File "/app/api/.venv/lib/python3.12/site-packages/botocore/endpoint.py", line 119, in make_request
return self._send_request(request_dict, operation_model)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/app/api/.venv/lib/python3.12/site-packages/botocore/endpoint.py", line 200, in _send_request
while self._needs_retry(
^^^^^^^^^^^^^^^^^^
File "/app/api/.venv/lib/python3.12/site-packages/botocore/endpoint.py", line 360, in _needs_retry
responses = self._event_emitter.emit(
^^^^^^^^^^^^^^^^^^^^^^^^^
File "/app/api/.venv/lib/python3.12/site-packages/botocore/hooks.py", line 412, in emit
return self._emitter.emit(aliased_event_name, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/app/api/.venv/lib/python3.12/site-packages/botocore/hooks.py", line 256, in emit
return self._emit(event_name, kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/app/api/.venv/lib/python3.12/site-packages/botocore/hooks.py", line 239, in _emit
response = handler(**kwargs)
^^^^^^^^^^^^^^^^^
File "/app/api/.venv/lib/python3.12/site-packages/botocore/retryhandler.py", line 207, in call
if self._checker(**checker_kwargs):
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/app/api/.venv/lib/python3.12/site-packages/botocore/retryhandler.py", line 284, in call
should_retry = self._should_retry(
^^^^^^^^^^^^^^^^^^^
File "/app/api/.venv/lib/python3.12/site-packages/botocore/retryhandler.py", line 320, in _should_retry
return self._checker(attempt_number, response, caught_exception)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/app/api/.venv/lib/python3.12/site-packages/botocore/retryhandler.py", line 363, in call
checker_response = checker(
^^^^^^^^
File "/app/api/.venv/lib/python3.12/site-packages/botocore/retryhandler.py", line 247, in call
return self._check_caught_exception(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/app/api/.venv/lib/python3.12/site-packages/botocore/retryhandler.py", line 416, in _check_caught_exception
raise caught_exception
File "/app/api/.venv/lib/python3.12/site-packages/botocore/endpoint.py", line 279, in _do_get_response
http_response = self._send(request)
^^^^^^^^^^^^^^^^^^^
File "/app/api/.venv/lib/python3.12/site-packages/botocore/endpoint.py", line 383, in _send
return self.http_session.send(request)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/app/api/.venv/lib/python3.12/site-packages/botocore/httpsession.py", line 499, in send
raise ConnectTimeoutError(endpoint_url=request.url, error=e)
botocore.exceptions.ConnectTimeoutError: Connect timeout on endpoint URL: "http://storage.railway.internal:9000/difyai";
Pinned Solution
a year ago
Hello
From the logs, it shows that your app is timing out and while conneting to http://storage.railway.internal:9000/difyai.
- Make sure the storage service (likely MinIO) is running and in the same Railway project.
- Double-check the
STORAGE_ENDPOINTURL in your.env— it must point to the correct internal service name. - On Railway, use the correct internal hostname like
http://<service-name>.railway.internal:9000.
2 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 chandrika • 12 months ago
a year ago
Hello
From the logs, it shows that your app is timing out and while conneting to http://storage.railway.internal:9000/difyai.
- Make sure the storage service (likely MinIO) is running and in the same Railway project.
- Double-check the
STORAGE_ENDPOINTURL in your.env— it must point to the correct internal service name. - On Railway, use the correct internal hostname like
http://<service-name>.railway.internal:9000.
idiegea21
Hello From the logs, it shows that your app is timing out and while conneting to <http://storage.railway.internal:9000/difyai>_._ * Make sure the storage service (likely MinIO) is **running** and **in the same Railway project**. * Double-check the `STORAGE_ENDPOINT` URL in your `.env` — it must point to the correct internal service name. * On Railway, use the correct internal hostname like `http://<service-name>.railway.internal:9000`.
a year ago
@idiegea21 Thanks for helping in detailed info! You're absolutely right, it's due to the issue with MinIO storage. Still I have no idea how to fix it but it's the root cause.
Status changed to Solved chandrika • 11 months ago