https proxy settings in openmediavault with a http-proxy for https traffic

1st Official Post

    Hello :)


    in openmediavault you are able to specify proxy settings.


    This happens under Network - Proxy Settings


    Here I can make settings for a http and https proxy. In our case we use a http proxy for both http and https connections.


    But in the settings in openmediavault under the settings for a https proxy I can only enter the host, port, username and password, but not the protocol.


    These settings are then transferred to the file etc/profile.d/10openmediavault-proxy.sh as follows:


    export http_proxy="http://proxy.example.com:8080"

    export HTTP_PROXY="${http_proxy}"

    export https_proxy="https://proxy.example.com:8080"

    export HTTPS_PROXY="${https_proxy}"


    I would need it like this though:

    export http_proxy="http://proxy.example.com:8080"

    export HTTP_PROXY="${http_proxy}"

    export https_proxy="http://proxy.example.com:8080"

    export HTTPS_PROXY="${https_proxy}"


    Based on the fact that I can't select a protocol for the proxy server under the https settings in openmediavault, it looks like a bug to me, since a description export https_proxy="http://proxy.example.com:8080" is generally allowed.


    How do you guys see this? Is this a bug or should this be more of a feature enhancement request?


    Best regards

    Christoph

  • votdev

    Added the Label resolved

  • votdev

    Added the Label OMV 6.x

    Hello Volker,


    thanks again for your help.


    I have upgraded to the current version and I was able to enter the proxy settings in the host now as follows:


    http://proxy.example.com


    The settings in /etc/profile.d/10openmediavault-proxy.sh are now also adjusted correctly.


    Unfortunately you forgot the settings in apt. In the /etc/apt/apt.conf.d/99openmediavault-proxy file, the setting shows now https://http://proxy.example.com when I enter http://proxy.exmaple.com in the openmediavault proxy settings:






    Could you please adjust this as well?


    Thanks in advance

    Christoph

    • Official Post

    Thx for reporting. The issue will be fixed in openmediavault 6.0.42-2, see https://github.com/openmediava…fe2f65913a74b02b755bc8578.

    Hi all
    I had the same problem using http only proxy, but following the above suggerstions, now it works fine (when installing update through the OMV's web interface).


    Only when I install updates via ssh :

    Code
    apt update && apt upgrade

    then I see warning messages like this :

    Code
    W: Failed to fetch https://openmediavault.github.io/packages/dists/shaitan/InRelease  Could not handshake: An unexpected TLS packet was received. [IP: proxy_ip port]
W: Some index files failed to download. They have been ignored, or old ones used instead.

    - is this a malfunction of the system ?

    - if updates from web interface works correctly and I should NOT update from the terminal then I am ok with this !!


    I am new to OMV so forgive my ignorance


    regards

    Quote from alexxtasi

    f updates from web interface works correctly and I should NOT update from the terminal then I am ok with this !!

    On CLI, try with omv-upgrade.

    This is the command ran by the GUI.


    Do not use apt upgrade

    Quote from Soma

    On CLI, try with omv-upgrade.

    This is the command ran by the GUI.


    Do not use apt upgrade

    Hi Soma and thanks for the quick reply.


    When running  omv-upgrade  I have the same messages :

    Code
    W: Failed to fetch https://openmediavault.github.io/packages/dists/shaitan/InRelease  Could not handshake: An unexpected TLS packet was received. [IP: proxy_ip port]
W: Some index files failed to download. They have been ignored, or old ones used instead.

    Any suggestions ?


    And also another question :

    Quote

    Do not use apt upgrade

    Is  omv-upgrade  just preferable than  apt upgrade  or it will "damage" the system ?


    Thanks in advance

    Quote from alexxtasi

    Any suggestions ?

    Sorry but that is way out of my league.

    I don't use proxy so, can't help you on that.


    Maybe you can comment out that repo and use the other one that is a mirror:

    packages.openmediavault.org

    AAAA for packages.openmediavault.org? - Network - openmediavault


    If you try to test this, make a copy of any files you're going to change/edit.

    And, even better, have a cloned backup of the system drive, NOW is a good time as any.


    Quote from alexxtasi

    Is omv-upgrade just preferable than apt upgrade or it will "damage" the system ?

    omv-upgrade script runs more that just upgrade so, it's preferable.


    Using apt upgrade won't damage the system.

    But the script is there to do it's work.

    Thanks again Soma for your help.


    So if anyone can help...

    I edited openmediavault.list file in directory /etc/apt/sources.list.d/ (made a backup of course :) ).

    Now it's :

    Code
    root@omv:~# cat /etc/apt/sources.list.d/openmediavault.list 
deb http://packages.openmediavault.org/public/ shaitan main
#deb https://openmediavault.github.io/packages/ shaitan main
# deb http://downloads.sourceforge.net/project/openmediavault/packages/ shaitan main

    Now when I run omv-upgrade I have no warnings !!

    Is this a normal operation ? Should I leave it as is or that line of sources is crucial ?


    regards

    Quote from alexxtasi

    Now when I run omv-upgrade I have no warnings !!

    Is this a normal operation ? Should I leave it as is or that line of sources is crucial ?

    I just checked the VM I run:

    Code
    root@omv6teste:~# cat /etc/apt/sources.list.d/openmediavault.list
deb http://packages.openmediavault.org/public/ shaitan main
deb https://openmediavault.github.io/packages/ shaitan main
# deb http://downloads.sourceforge.net/project/openmediavault/packages/ shaitan main


    After, I commented the line:

    Code
    root@omv6teste:~# cat /etc/apt/sources.list.d/openmediavault.list
deb http://packages.openmediavault.org/public/ shaitan main
#deb https://openmediavault.github.io/packages/ shaitan main
# deb http://downloads.sourceforge.net/project/openmediavault/packages/ shaitan main

    And the output of omv-upgrade:


    So, you're not hitting repos on http only.


    Maybe this gives you an idea of what's going on.

    Whether this is considered a bug or a feature enhancement depends on the intended design of OpenMediaVault and its proxy settings. If the omission of the protocol selection for HTTPS proxies is unintentional or results in unexpected behavior, it could be considered a bug. On the other hand, if it's a deliberate design choice or a feature that hasn't been implemented yet, it might be categorized as a feature enhancement request.

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!

Register Yourself Login