While hosting an application that we use Puppeteersharp on IIS, I get a 407 error. I make the relevant proxy settings, but I still keep getting the same error.
I tried each of the settings in the picture, but the result did not change. I'm sure the username and password are correct.
When I run the application exe, it goes to the internet without being connected to the proxy, but IIS does not come out either.
How do i solve this problem?
I faced the same problem. This is probably caused by the puppeteersharp library that is running under your project. The library may be going to another url to configuration some settings. So the proxy server may be blocking these urls. You can detect this url and allow it. I couldn't solve the problem then i changed my library as selenium. This solve my problem in IIS.
Related
I provided incorrect subdomain name during Kabanero Foundation installation on OKD. Now my Application-->Routes are wrong. How to fix that?
For Kabanero Landing Page, my link is: https://kabanero-landing-kabanero./
I tried https://kabanero-landing-kabanero./ but I get
Application is not available
The application is currently not serving requests at this endpoint. It may not have been started or is still starting.
Expected: Kabanero Landing Page
Actual: Application is not available
The application is currently not serving requests at this endpoint. It may not have been started or is still starting.
There really is no good way to fix it. There is not a good manner to change the routes automatically. Assuming you are early in your install, you should be able to clone the 0.2.0 (if you installed 0.2.0) support scripts from https://github.com/kabanero-io/kabanero-foundation/tree/0.2.0/scripts and run the uninstall-kabanero-foundation.sh script to remove the foundation and reinstall. You should be able to keep the OKD install that you have done.
If there are enough people that hit this, I can put a requirement in place to provide an update script to change this value and restart.
I have a legacy ISAPI dll, that generally fulfills requests just fine, but occasionally I will get prompted to save the dll from my browser. This is a known issue, with some good workarounds. IIS 8.5 serving dll for download instead of executing Hitting download will give you a zero byte file.
I am actually interested in doing the opposite of the workaround. How can I force this (incorrect) behavior, ie, is it possible to trick the server to download the full ISAPI dll? If so, what settings should I change. I am running IIS 7.5.
[EDIT] For clarity, I am not trying to hack anything client side. I doubt that's possible, but if it is I would really like to know. I am trying to figure out if it is possible to get the server to give up the dll with just a plain old post/get request. This is how I got it to give me the dll the first time, luckily it was zero bytes.
Thank you
I have question about how to set Node.js server application. On my server I have ColdFusion application server. I can test my code through browser url. I would like the same for Node.js. Node is already installed on my server but the only way to run the code is through cmd command window. First question is what I need in order for both to run on the same server? I still need my ColdFusion. Second question is about Nodes.js and can I set up server application with ISS or I need something else? Also do I have to specify what extension on my files will point to ColdFusion and other to Node. For example .cfm extension is for ColdFusion and .js is for the Node. If anyone knows anything about this or where I can find more information please let me know. I never experienced something similar and this is something completely new for me.
I know this is an old post but I figure I'd provide an answer for those souls who are looking around.
If working with Apache 2.4.x.
In a test environment this would not be to much of an issue as Node and Coldfusion operate on different ports.
If your looking to create a production site than I would say that building a virtual host with proxy to the node site and Coldfusion would be another method.
If you are using the Coldfusion connector to Apache and loading node, than still loading the proxy for the node part would be fine, just make sure you are pointing to the correct port for your node.
Things to remember:
You may have to alter internal Firewall rules.
Comment your hosts files so you don't accidentally alter the wrong file.
Both can exist within the same platform.
I put a basic, no frills node npm-express blog site up on a azure website and the IIS load balancing or just iisnode itself seemed to cause issues running the app.js. Running outside of IIS didn't experience any issues. No websockets, just express using vash templates.
The issues I ran into are:
Using web deploy and some node_modules intermittently not deploying. npm lwip for instance would work at first then wouldn't if deploying again. Sometimes other js and vash files would not update also.
When using the site there was a plain vash templates section (the public facing side) and a login side of the site. The simple one page public facing side would intermittently create a 500 error. One out of every three request would do this. No logs generated and all logging was turned on. The error was from iisnode and not node itself.
Using visual studio 13 with all the latest updates, remote debugging simply didn't work. Basically in the dark. Oddly the logged in portion using npm-passport-local worked but that never changed domains when using. It was only the pages on the public side that this would happen. FYI, the public side had multiple domains and various sub domains pointing to the site. All entered correctly in the azure portal and would work with the intermittent 500 error. The page had links to other blogs with full urls, hence the domain would change. Which should be an issue but I suspect had something to do with it.
I ended up having to create a azure vm and install node on it myself to get the site working without the use of IIS. FYI, running the node site locally on my sand I never encountered any issues either.
Has anyone else experienced issues like this using iisnode and did you find a work around for this?
I suspect it may happen when multiple domains are used for the same instance.
I have successfully tested the vline-node example locally, but would like to push it out to a server. I have tried to install the example as an application on an IIS8 website, placing the example code under wwwroot. I have done tried this both within the root and inside a virtual directory, pointing to the views folder. I am able to login to the application from a browser on the server, although, since javascript is turned off on the server browsers for security, so functionality is missing.
However, when I try to access the site from a remote browser I am not able to login. Actually, I can see that there is something wrong with my paths, as the include files are not found.
The more I've thought about this the more confused I've become. I'd like to run this under IIS, but wonder if that makes sense. Can someone offer a clean solution for hosting the vline-node example on a Windows Server, ideally under IIS?
Since you are using the node example, you'll need to make sure that node is actually running on your IIS server. Here's a SO response that may be helpful: How to run Node.JS server for a web application?
Note that in our node example the "main" file is vline-node.js, so use that in place of the app.js that is mentioned.