We installed Microsoft Workflow Manager on our SharePoint farm. When we first added the WF node, we configured not to allow http. For testing, we want to how allow HTTP.
The command update-WFHost does not seem to have a parameter for -EnableHttpPort.
We can remove the node and add back but was hoping to be able to make the change via a command.
Open IIS Manager.
Select Workflow Management Site in left pane.
Press "Bindings" button in right pane.
Add binding for HTTP protocol (port must be different from port for HTTPS).
Open PowerShell and execute cmdlet Register-SPWorkflowService with setting value of parameter "WorkflowHostUri" to new http binding.
Related
I have 3 sites(virtual directories) registered under the Default Web Site in IIS, those can access like below:
http://localhost/Site1
http://localhost/Site2
http://localhost/Site3
Currently I have one port number which is port 80.
I need to setup those sites with https having different port numbers, like below:
https://demo.mydomain.com:5001/Site1
https://demo.mydomain.com:5002/Site2
https://demo.mydomain.com:5003/Site3
I am new to the IIS. Can someone please help me out with the approach to solve the above scenario?
is the domain already pointing to your webserver or are you trying to achieve this on you development machine?
If the domain is already pointing to the server, you can do this IIS by adding bindings to your websites (in your case its the defaultwebsite).
You can achieve this by right-clicking the website. Here you can see "Edit Bindings". You will have to add a binding foreach port. Just click on "add" and type in the right hostname (demo.mydomain.com) and the port. You can also choose a certificate here for the https connection.
If you are trying to achieve this on your dev machine, you will also have to add your hostname to the windows hosts-file. Under "C:\Windows\System32\drivers\etc\hosts" add the line "127.0.0.1 demo.mydomain.com".
Jonathan
I am trying to run a client application on the same server that hosts our IIS-hosted raven server (build 2947). The IIS site that hosts raven is bound to an SSL certificate/hostname - we would like to enforce secure requests only (and redirect http requests to https). When I set the connection to use the https protocol:
Url=https://ravendb.somewhere.net;Database=StaffDb
I get a 401 denied error when the connection is opened. If I disable the redirect and connect to localhost non-securely, it works fine:
Url=http://localhost;Database=StaffDb
The docs suggest SSL can only be enabled when running as a service - does this mean our scenario of running within a secure IIS site is not possible?
When using SSL, you must use the specified hostname in the certificate.
With thanks to Ayende Rahien for support provided offline, it turned out this issue is actually due to a feature of IIS itself:
Windows XP SP2 and Windows Server 2003 SP1 include a loopback check
security feature that is designed to help prevent reflection attacks
on your computer. Therefore, authentication fails if the FQDN or the
custom host header that you use does not match the local computer
name.
Ayende's blog provides some more context, and I fixed this by following steps outlined in a Microsoft support article:
Method 2: Disable the loopback check (less-recommended method) The second method is to disable the loopback check by setting the
DisableLoopbackCheck registry key.
To set the DisableLoopbackCheck registry key, follow these steps:
.....
2. Click Start, click Run, type regedit, and then click OK.
3. In Registry Editor, locate and then click the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
4. Right-click Lsa, point to New, and then click DWORD Value.
5. Type DisableLoopbackCheck, and then press ENTER.
6. Right-click DisableLoopbackCheck, and then click Modify.
7. In the Value data box, type 1, and then click OK.
8. Quit Registry Editor, and then restart your computer.
I am trying the Browserlink feature of ASP.NET MVC 5 and everything works great for non SSL pages. But if I navigate to a SSL page (with https url), I see 0 connections in the Browser link dashboard. So, is it true that Browser link works only for non SSL urls ? Or am I am missing any settings which will allow me to get Browser Link connection for both SSL and Non SSL urls ?
(I am testing from IIS)
According to this link, Microsoft is working on it.
I have been able to get around the issue by following these steps (using Chrome):
When the debugger opens the browser, open the F12 tools.
Go to the Console tab.
There should be an error message that looks something like this: GET https://localhost:[port]/[guid]/browserLink net::ERR_INSECURE_RESPONSE
Open the link in a new tab.
Click Proceed anyway.
Close the Browser Link tab.
Reload the tab with your app.
Browser Link should then start working.
I've also worked around it by getting the script link, reducing it to the root, and browsing there. Once there, accept the cert warning then view the cert and install it into the trusted roots. From then on, the cert will be trusted and the script will load automatically.
It appears that this limitation has been removed in Visual Studio 2015. I do not see any mention of this in the release notes, but Browser Link is fully operational in my dev environment under SSL.
I was unable to get Browser Link, Web Essentials, to work with SSL, even with the mentioned remedies. I was able to find a way, however, to get it work for me.
I am running my app through IIS (not express) and my app was nested under the default website. When debugging the site I saw that Chrome was dumping a connection error with a URL using port 44399. Adding a binding for this port, for https, then allowed the connection to be successful. I also used a local development cert for the SSL Certificate.
DISCLAIMER: Visual Studio tries to be your buddy and not use ports that you've bound to in IIS so once you close and re-open Visual Studio it will likely not use the 44399 port anymore. It looks like it decrements until it finds the next available port. So assuming you're not using 44398 this will be your number. Once you unbind 44399, then close and re-open Visual Studio it will likely rebind to 44399 again.
Hopefully this helps some of you out.
I had a similar issue involving custom domains and subdomains on IIS Express over HTTPS.
(Using SSL certificate I self-signed with support for localhost and my custom domain, installed with self-signed root authority in the trusted certificate store)
I had got IISEx to use the certificate and serve it on port 443 (as admin user), but browserlink was failing with CONNECTION_RESET.
This persisted even after switching back to using localhost as the website url for IIS etc.
Turns out I had forgotten to replace the certificate associated with the other ports IIS Express uses (specifically port 44399), which were still associated with the default development certificate used by IIS Express
http://www.iis.net/learn/extensions/using-iis-express/handling-url-binding-failures-in-iis-express
http://benjii.me/2014/11/run-iis-express-on-port-443-using-ssl-and-wildcard-subdomains/
[Simple Guide but missing the delete existing certificate bindings guidance]
For Windows 10 IIS Express users.
In visual studio click "View in Browser" in Browser Link
Dashboard .
An IIS Express icon will appear in system tray.
Right Click the IIS Express icon.Your application should be listed in both HTTP and HTTPS.
Hope it helps.
On an IIS server with Application Request Routing, new server farms to be routed to can be added by right-clicking Server Farms -> Create Server Farm.
This will pop up a dialog where the settings for the server farm can be entered. I did not manage to find a way to edit or view these settings after they are accepted in the Create-Serverfarms-dialog.
My question is therefore: How can I edit the target-url, http-port and https-port settings of a server farm outside of the create-serverfarm dialog?
You could use the command line to do so.
For example, lets say we have a Server Farm called test with one application server www.example.com in it:
All the following commands need to be run in the %windir%\system32\inetsrv directory unless you have it in your PATH.
To change the target-url of the application server to www.google.com, use:
appcmd.exe set config /section:webFarms /"[name='test'].[address='www.example.com']".address:www.google.com
You can change any parameters the way you would do it with the dialog (and even more).
To get the list of parameters you can use with the command line:
appcmd.exe set config -section:webFarms -?
And particularly the section you seem to be interested by:
And finally, to view the current config of your server farm:
appcmd.exe list config /section:webFarms
Should get you something like:
References:
http://www.iis.net/learn/get-started/getting-started-with-iis/getting-started-with-appcmdexe
http://www.iis.net/learn/extensions/configuring-application-request-routing-(arr)/define-and-configure-an-application-request-routing-server-farm
Update:
You may generate PowerShell script from IIS Manager.
Web Server (IIS) Administration Cmdlets in Windows PowerShell
Also, you may edit C:\Windows\System32\inetsrv\config\applicationHost.config file manually.
I have a test Sharepoint server running on a Windows 7 machine. The url is http://liu-t500-01 and i want to create a user friendly alias http://temp for it. i have added
127.0.0.1 temp
to my hosts file (an A/host entry) and i have also created an alternate access mapping in Central Administration
http://liu-t500-01 Default http://liu-t500-01
http://temp Intranet http://temp
However when i try http://temp in the browser the sharepoint site does not come up. This is probably a simple problem but has me scratching my head...what did i do wrong?
Changing the IIS binding only will cause errors. You need to modify the alternate access mappings in SharePoint. There are tons of good articles our there that tell what to do in detail.
Here is just one: http://technet.microsoft.com/en-us/sharepoint/Video/ff679917
Try adding a host header in IIS
In IIS click on your site
choose the Bindings action
Click Add
In the Host Name field enter "temp"
click OK