Skip to main content

Setting up Proxy for debian OS using CLI

Create proxy file using VIM or nano 

sudo vim /etc/profile.d/proxy.sh

Populate your proxy values.

# set proxy config via profie.d - should apply for all users
# http/https/ftp/no_proxy
export http_proxy="http://192.10.1.20:8080/"
export https_proxy="http://192.10.1.20:8080/"
export ftp_proxy="http://192.10.1.20:8080/"
export no_proxy="127.0.0.1,localhost"

# For curl
export HTTP_PROXY="http://192.10.1.20:8080/"
export HTTPS_PROXY="http://192.10.1.20:8080/"
export FTP_PROXY="http://192.10.1.20:8080/"
export NO_PROXY="127.0.0.1,localhost"

Add any additional IP address to be excluded to the NO_PROXY & no_proxy environment variables. When done add execution bit to the script created.

sudo chmod +x /etc/profile.d/proxy.sh

Source the file for runtime use:

source /etc/profile.d/proxy.sh

Confirm proxy has been loaded in your environment.

$ env | grep -i proxy

Comments

Popular posts from this blog

Deploy OVF fails Issues detected with selected template. Details: VALUE_ILLEGAL: No supported hardware versions among [virtualbox-2.2]; supported: [vmx-04, vmx-07, vmx-08, vmx-09, vmx-10, vmx-11, vmx-12, vmx-13, vmx-14, vmx-15, vmx-16, vmx-17, vmx-18, vmx-19].

 Error: While deploy using OVF file ,getting error as : Issues detected with selected template. Details: - -1:-1:VALUE_ILLEGAL: No supported hardware versions among [virtualbox-2.2]; supported: [vmx-04, vmx-07, vmx-08, vmx-09, vmx-10, vmx-11, vmx-12, vmx-13, vmx-14, vmx-15, vmx-16, vmx-17, vmx-18, vmx-19]. Solution: Open .OVF file and edit       <Info>Virtual hardware requirements for a virtual machine</Info>       <System>         <vssd:ElementName>Virtual Hardware Family</vssd:ElementName>         <vssd:InstanceID>0</vssd:InstanceID>         <vssd:VirtualSystemIdentifier>zabbix_appliance-6.2.7</vssd:VirtualSystemIdentifier>         <vssd:VirtualSystemType> virtualbox-2.2 </vssd:VirtualSystemType>       </System> to  vmx-19       <Info>Virtual hardware requireme...

Change ESXi acceptane level of VIBs to community Supported

-When you install VIB bundles you may see issue like:               'Could not find a trusted signer: self signed certificate  For resolving this issue, we have to convert the ESXi to community supported acceptance level. -To do that: if  ESXI is a VM :      Edit settings ->boot option ->disable secure boot. if Physical ESXi:      Edit  UEFI Now ssh to ESXi: - Move the ESX machine to community-support esxcli software acceptance set --level=CommunitySupported - Install the bundle with no-sign-check esxcli software vib install -d  VMware_bootbank_vmware-fdm_7.0.1-16478307.vib --no-sig-check -  Set back PartnerSupported esxcli software acceptance set --level=PartnerSupported