Astro CLI ‘astro dev start’ failing, where to setup proxy

Astro CLI
1

On Oracle Linux 8,8 server, I installed the astro-cli using the astro documentation.
After creating a folder astro, enter in it, give astro dev init
On astro dev start - encountered an error and the server did not start - 8080 not available.
Used the troubleshooting link and entered astro dev logs --scheduler
Found an error at at update_checks.py - Connection to updates.astronomer.io timed out.
Can you please tell me how to setup proxy so astro-cli can bypass firewall ?
I already setup Proxy Settings in /etc/yum.conf and in Dockerfile - not sure if they do anything.
Or how can I disable the update checks for a new version in astro-cli ?

Astro2
Astro21699×944 418 KB

2

Hi @bbsoft0 ,
I have the same problem on Ubuntu 22.04 WSL on Windows. XXX stands for my proxy-url

I tried the following things

  1. Setting ENV-Variables in Dockerfile → NOT WORKING
    USER root
    ENV http_proxy=XXX
    ENV https_proxy=XXX
    ENV HTTPS_PROXY=XXX
    ENV HTTP_PROXY=XXX

USER root
RUN export http_proxy=XXX
RUN export https_proxy=XXX
RUN export HTTP_PROXY=XXX
RUN export HTTPS_PROXY=XXX

  1. Tried to add docker-compose.override.yml with the following content. See Run your Astro project in a local Airflow environment with the CLI | Astronomer Documentation
    version: ‘3.4’
    services:
    scheduler:
    environment:
    HTTP_PROXY: XXX
    HTTPS_PROXY: XXX
    http_proxy: XXX
    https_proxy: XXX
    When I was logged in to the scheduler bash via astro dev bash --scheduler the value was set → echo $http_proxy. But I was getting an Authentication error from the proxy
    File “/usr/local/lib/python3.11/site-packages/requests/adapters.py”, line 513, in send
    raise ProxyError(e, request=request)
    requests.exceptions.ProxyError: HTTPSConnectionPool(host=‘updates.astronomer.io’, port=443): Max retries exceeded with url: /astronomer-runtime?site=http%3A%2F%2Flocalhost%3A8080 (Caused by ProxyError(‘Unable to connect to proxy’, OSError(‘Tunnel connection failed: 407 authenticationrequired’)))

Can you try if theses opportunities work in your environment?
What is the problem on my second point? Any suggestions?
Are there other opportunities to set the proxy?
Thanks Chris

1 Like
3

Opportunity 2 worked for me (Error was caused by our proxy)

1 Like