Originally created by @DeBruyxuan on GitHub (Feb 17, 2025).
problem description
I set up my own cobalt service about three weeks ago and everything was running fine, but I recently encountered 'api.youtube.login' problem. What should I do? Change proxy or use cookie.json?
The following is my yml code
`services:
cobalt-api:
image: ghcr.io/imputnet/cobalt:latest
restart: unless-stopped
container_name: cobalt-api
init: true
ports:
- 9002:9000/tcp
# if you're using a reverse proxy, uncomment the next line and remove the one above (9000:9000/tcp):
#- 127.0.0.1:9000:9000
environment:
API_URL: "http://xxxxxx.com/"
# if you want to use cookies when fetching data from services, uncomment the next line and the lines under volume
# COOKIE_PATH: "/cookies.json"
# see docs/run-an-instance.md for more information
labels:
- com.centurylinklabs.watchtower.scope=cobalt
# if you want to use cookies when fetching data from services, uncomment volumes and next line
#volumes:
#- ./cookies.json:/cookies.json
# update the cobalt image automatically with watchtower
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`
your instance configuration
Originally created by @DeBruyxuan on GitHub (Feb 17, 2025).
### problem description
I set up my own cobalt service about three weeks ago and everything was running fine, but I recently encountered 'api.youtube.login' problem. What should I do? Change proxy or use cookie.json?
The following is my yml code
`services:
cobalt-api:
image: ghcr.io/imputnet/cobalt:latest
restart: unless-stopped
container_name: cobalt-api
init: true
ports:
- 9002:9000/tcp
# if you're using a reverse proxy, uncomment the next line and remove the one above (9000:9000/tcp):
#- 127.0.0.1:9000:9000
environment:
API_URL: "http://xxxxxx.com/"
# if you want to use cookies when fetching data from services, uncomment the next line and the lines under volume
# COOKIE_PATH: "/cookies.json"
# see docs/run-an-instance.md for more information
labels:
- com.centurylinklabs.watchtower.scope=cobalt
# if you want to use cookies when fetching data from services, uncomment volumes and next line
#volumes:
#- ./cookies.json:/cookies.json
# update the cobalt image automatically with watchtower
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`
### your instance configuration
```shell
```
haha ignore that. could you tell me what's wrong with my service?
@DeBruyxuan commented on GitHub (Feb 17, 2025):
> > youdao.com
>
> do you work for netease?
haha ignore that. could you tell me what's wrong with my service?
I add http_proxy and https_proxy in environment in yml,but it doesn't work
@DeBruyxuan commented on GitHub (Feb 17, 2025):
> > youdao.com
>
> do you work for netease?
I add http_proxy and https_proxy in environment in yml,but it doesn't work
I add http_proxy and https_proxy in environment in yml,but it doesn't work
please read the documentation
@dumbmoron commented on GitHub (Feb 17, 2025):
> > > youdao.com
> >
> >
> > do you work for netease?
>
> I add http_proxy and https_proxy in environment in yml,but it doesn't work
please read the documentation
I add http_proxy and https_proxy in environment in yml,but it doesn't work
please read the documentation
thanks I've read that and add api_external_proxy.but it doesn't work
@DeBruyxuan commented on GitHub (Feb 17, 2025):
> > > > youdao.com
> > >
> > >
> > > do you work for netease?
> >
> >
> > I add http_proxy and https_proxy in environment in yml,but it doesn't work
>
> please read the documentation
thanks I've read that and add api_external_proxy.but it doesn't work
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @DeBruyxuan on GitHub (Feb 17, 2025).
problem description
I set up my own cobalt service about three weeks ago and everything was running fine, but I recently encountered 'api.youtube.login' problem. What should I do? Change proxy or use cookie.json?
The following is my yml code
`services:
cobalt-api:
image: ghcr.io/imputnet/cobalt:latest
restart: unless-stopped
container_name: cobalt-api
your instance configuration
@DeBruyxuan commented on GitHub (Feb 17, 2025):
I have set cookie.json but it still doesn't work
@wukko commented on GitHub (Feb 17, 2025):
do you work for netease?
@DeBruyxuan commented on GitHub (Feb 17, 2025):
haha ignore that. could you tell me what's wrong with my service?
@DeBruyxuan commented on GitHub (Feb 17, 2025):
I add http_proxy and https_proxy in environment in yml,but it doesn't work
@dumbmoron commented on GitHub (Feb 17, 2025):
please read the documentation
@DeBruyxuan commented on GitHub (Feb 17, 2025):
thanks I've read that and add api_external_proxy.but it doesn't work