I am developing a
node.js
proxy server application and I want it to support HTTP
and HTTPS(SSL)
protocols (as server).- Unable To Allocate Processing Resources On Host Proxy Requires Upgrade Download
- Veeam Upgrade Backup Proxy
- Veeam Unable To Allocate Processing Resources Requires Upgrade
I'm currently using
node-http-proxy
like this:I setup my browser to use
HTTP
proxy on localhost:8000
and it works. I also want to catch HTTPS
requests (ie. setup my browser to use localhost:8000
as HTTPS
proxy as well and catch the requests in my application). Could you please help me how can I do that?PS:
If I subscribe to
upgrade
event of httpProxy
server object I can get the requests but I don't know how to forward the request and send response to client:Any helps would be appreciated.
Skyrim how many followers. Please this article however you can remove this notice once finished.See full article: for more detailed information about followers. This table lists what those values mean.LegendYesNoReportYou can sneak with this followerYou cannot sneak while you have this followerYou can access their inventoryYou cannot access their inventory.You will get a for doing this in front of themThey will pick up stolen items for youThey will not pick up items off the ground that are stolenYou will get a bounty if you do it in front of them.MurderThey will kill anyone you ask them toThey will not kill innocent people for youThey will attack you if you kill an innocent person in front of them. Morality columnsThe table below has columns for certain actions, with 'Yes,' 'No,' or 'Report' listed.
user1051478
user1051478user1051478
4 Answers
Solutions barely exist for this, and the documentation is poor at best for supporting both on one server. The trick here is to understand that client proxy configurations may send https requests to an http proxy server. This is true for Firefox if you specify an HTTP proxy and then check 'same for all protocols'.
You can handle https connections sent to an HTTP server by listening for the 'connect' event. Note that you won't have access to the response object on the connect event, only the socket and bodyhead. Data sent over this socket will remain encrypted to you as the proxy server.
In this solution, you don't have to make your own certificates, and you won't have certificate conflicts as a result. The traffic is simply proxied, not intercepted and rewritten with different certificates.
y3shy3sh
Here is my NO-dependencies solution (pure NodeJS system libraries):
I tested this code with Firefox Proxy Settings (it even asks for username and password!). I entered IP address of machine where this code is runned and 9191 port as you can see in the code. I also set 'Use this proxy server for all protocols'. I run this code locally and on VPS - in both cases works!
You can test your NodeJS proxy with curl:
Unable To Allocate Processing Resources On Host Proxy Requires Upgrade Download
Alexey VolodkoAlexey Volodko
I have created a http/https proxy with the aid of the http-proxy module: https://gist.github.com/ncthis/6863947
Code as of now:
ncabralncabral2,15311 gold badge1515 silver badges1818 bronze badges
The node-http-proxy docs contain examples of this. Look for 'Proxying to HTTPS from HTTPS' at https://github.com/nodejitsu/node-http-proxy The configuration process is slightly different in every browser. Some have the option to use your proxy settings for all protocols; some you need to configure the SSL proxy separately.
Michael BrundageMichael Brundage
Not the answer you're looking for? Browse other questions tagged httpnode.jssslhttpsproxy or ask your own question.
When I run
sudo
the terminal is stuck for a few seconds and then outputs an error message. My terminal looks like this:What can I do to solve it?
Kit Sunde
Kit SundeKit Sunde4,25677 gold badges1919 silver badges2929 bronze badges
20 Answers
Two things to check (assuming your machine is called
my-machine
, you can change this as appropriate):- That the
/etc/hostname
file contains just the name of the machine. - That
/etc/hosts
has an entry forlocalhost
. It should have something like:
If either of these files aren't correct (since you can't sudo), you may have to reboot the machine into recovery mode and make the modifications, then reboot to your usual environment.
Thomas Ward♦46.6k2323 gold badges128128 silver badges182182 bronze badges
Jeremy KerrJeremy Kerr20.2k33 gold badges4141 silver badges5959 bronze badges
Edit
/etc/hosts
and append your new hostname to the 127.0.0.1 line (or create a new line if you prefer that).Mine looks like:
Replace
penguin
in the above example by your new hostname as stated in the /etc/hostname
file.Community♦
LekensteynLekensteyn127k5050 gold badges272272 silver badges365365 bronze badges
Collin AndersonCollin Anderson2,55511 gold badge1111 silver badges99 bronze badges
Note, this is an answer to this question which has been merged with this one.
Your hostname (
dave00-G31M-ES2L
) is not represented in /etc/hosts
. Add an L
to this line:So it becomes:
In order to accomplish this, open a console (press Ctrl+Alt+T) and type:
Add the letter
L
as mentioned, save and exit.Community♦
ThorThor
I had this issue when I was using ubuntu on a VPS. I solved it editing /etc/hosts file.
run this command:
and then add:
I hope that will solve your issue :)
PS: Remember to reboot your computer!
Luca D'AmicoLuca D'Amico
I was having the same issue even though the hostname in my /etc/hostname file and /etc/hosts file matched.
My hostname was 'staging_1'. It turns out that you can't have an underscore in your hostname, which is why I was getting this error. Changing the underscore to a hyphen fixed my problem.
Chris.BChris.B
In AWS, go to your vpc and turn on 'DNS Hostnames'.
ErickErick
I encountered this same error message. I think this discussion thread at AWS Developer Forums is a better solution:
'Go the the VPC management console, select the VPC, click on Actions, select Edit DNS Hostnames and select Yes.'
user93581user93581
Some terminal emulators will not update prompt with the correct hostname until you close and restart the emulator (lxterminal, I'm talking to you).
I spent 30min fighting with this error after editing my hostname and hosts files and running
sudo service hostname restart
until I ran sudo hostname
and saw that the hostname was the new value, even though the prompt was showning the old value.dagbeldagbel
In my case it was the problem, I changed the
hostname
to man
because I wanted to know if there are some parameters you can use on hostname
. Instead it changed my hostname
to man
and I always got the same message like you after changing the hostname back to `localhost everything worked fine again
XandruCeaXandruCea
The symptom given in the question may correlate strongly with this more specific problem:
There are different ways that this could be resolved, one of which is to add your hostname as localhost in
/etc/hosts
(as shown in several other answers). This may be the right thing to do in general, but it isn't the only possible resolution.A 'fully qualified domain name' may be supplied by an external DNS server or similar (if such is available on your network). In this case,
sudo
will not complain, despite the missing entry in /etc/hosts
.Note:
sudo
attempts to dereference the hostname, even though it isn't necessarily required, due to optional capabilities in the sudoers file. See sudo command trying to search for hostname.As long as the delay isn't too long, this error message is typically harmless.
nobarnobar1,63622 gold badges1616 silver badges2727 bronze badges
Everybody advises to modify
/etc/hosts
. But in some cases this may not be possible (for example inside a docker container). So, I had to find a better way and I came up with this:Aliases don't work in bash scripts, but we can use variables:
sudo='sudo -h 127.0.0.1'
dashohoxhadashohoxha
Sorry I can't help you much but, since it says 'can't resolve host' try running:
And see if the output is the hostname of the machine. If not, the problem is the host configuration, not sudo.
animaletdesequiaanimaletdesequia6,80044 gold badges1919 silver badges3838 bronze badges
OP wrote:
It was all in /etc/hostname. On two of our sick servers it looked like this:
While on a server without this issue we had:
Removed the
linux-web-n
portion, rebooted and everything was fine.you might be getting an error if your hosts or hostname file contain illegal characters. Only these symbols are permitted: a-z, A-Z, 0-9
MarcelloMarcello
I had this same problem! I changed my VPS's name through the online admin control panel which did not change the machine name in the hosts file All I did was run:
Then I edited it from this:
To this:
and that fixed my error! Hope this helped!
SynthSynth
I had the same problem. I solved it by editing the /etc/hosts and /etc/hostname files.. on the /etc/hosts file, just edit the top part as shown below.
CentyCenty
if you can't sudo you CAN log in as root via su.IE: su root (in an x-term).then give the root password when prompted, then you can edit the files with nano. The root password in 'buntu is the same as the password you would use for sudo.
Veeam Upgrade Backup Proxy
ken scharfken scharf
If you are using Vagrant, then login into the guest and run
apt-get --no-install-recommends install virtualbox-guest-utils
tanmoytanmoy
In case your problem is that
/etc/hostname
file and /etc/hosts
, both files have your desired hostname and still your machine is showing the errorVeeam Unable To Allocate Processing Resources Requires Upgrade
sudo: unable to resolve host
Try, forcing the hostname
You will probably still get the same error, but try logging out and logging back in. It worked for me.
GypsyCosmonautGypsyCosmonaut
protected by Community♦Mar 31 '17 at 3:42
Thank you for your interest in this question. Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?
Would you like to answer one of these unanswered questions instead?