Souncloud URLs timeout #694

Closed
opened 2025-11-09 09:56:06 -06:00 by GiteaMirror · 1 comment
Owner

Originally created by @SlmnFz on GitHub (Jan 26, 2025).

problem description

I am running my own instance of cobalt using docker, it works and all the services are up.
I have tested instagram and twitter links and they work too, but when i send a soundcloud URL, i dont get any answer and i get 504 error (gateway timeout)

Image

Image

your instance configuration

services:
    cobalt-api:
        image: ghcr.io/imputnet/cobalt:10

        init: true
        read_only: true
        restart: unless-stopped
        container_name: cobalt-api

        ports:
            #- 1234:1234/tcp
            # if you use a reverse proxy (such as nginx),
            # uncomment the next line and remove the one above (9000:9000/tcp):
            - 127.0.0.1:1234:1234

        environment:
            # replace https://api.url.example/ with your instance's url
            # or else tunneling functionality won't work properly
            API_URL: "https://myurl/"
            API_NAME: "FzCobalt"
            API_PORT: 1234
            # if you want to use cookies for fetching data from services,
            # uncomment the next line & volumes section
            # COOKIE_PATH: "/cookies.json"

            # it's recommended to configure bot protection or api keys if the instance is public,
            # see /docs/protect-an-instance.md for more info

            # see /docs/run-an-instance.md for more variables that you can use here

        labels:
            - com.centurylinklabs.watchtower.scope=cobalt

        # uncomment only if you use the COOKIE_PATH variable
        # volumes:
            # - ./cookies.json:/cookies.json

    # watchtower updates the cobalt image automatically
    watchtower:
        image: ghcr.io/containrrr/watchtower
        restart: unless-stopped
        command: --cleanup --scope cobalt --interval 900 --include-restarting
        volumes:
            - /var/run/docker.sock:/var/run/docker.sock
Originally created by @SlmnFz on GitHub (Jan 26, 2025). ### problem description I am running my own instance of cobalt using docker, it works and all the services are up. I have tested instagram and twitter links and they work too, but when i send a soundcloud URL, i dont get any answer and i get 504 error (gateway timeout) ![Image](https://github.com/user-attachments/assets/cb557f88-b2d5-4003-afc6-3e7b2c9a46bf) ![Image](https://github.com/user-attachments/assets/ed37c3b4-6318-4141-b949-7b2d4e032cc8) ### your instance configuration ```shell services: cobalt-api: image: ghcr.io/imputnet/cobalt:10 init: true read_only: true restart: unless-stopped container_name: cobalt-api ports: #- 1234:1234/tcp # if you use a reverse proxy (such as nginx), # uncomment the next line and remove the one above (9000:9000/tcp): - 127.0.0.1:1234:1234 environment: # replace https://api.url.example/ with your instance's url # or else tunneling functionality won't work properly API_URL: "https://myurl/" API_NAME: "FzCobalt" API_PORT: 1234 # if you want to use cookies for fetching data from services, # uncomment the next line & volumes section # COOKIE_PATH: "/cookies.json" # it's recommended to configure bot protection or api keys if the instance is public, # see /docs/protect-an-instance.md for more info # see /docs/run-an-instance.md for more variables that you can use here labels: - com.centurylinklabs.watchtower.scope=cobalt # uncomment only if you use the COOKIE_PATH variable # volumes: # - ./cookies.json:/cookies.json # watchtower updates the cobalt image automatically watchtower: image: ghcr.io/containrrr/watchtower restart: unless-stopped command: --cleanup --scope cobalt --interval 900 --include-restarting volumes: - /var/run/docker.sock:/var/run/docker.sock ```
GiteaMirror added the instance hosting help label 2025-11-09 09:56:06 -06:00
Author
Owner

@dumbmoron commented on GitHub (Feb 8, 2025):

the link from your example downloads fine for me on the main instance, which indicates it's probably a problem with your network setup or internet provider

@dumbmoron commented on GitHub (Feb 8, 2025): the link from your example downloads fine for me on the main instance, which indicates it's probably a problem with your network setup or internet provider
Sign in to join this conversation.