I purchased sendy.
When I installed it in local it said "Unlicensed domain".
How to install it in localhost?
I tried a lot, but unsuccessfully.
Any help will be really appreciated.
You need to talk to the guys at Sendy. Installing and using Sendy requires a license which is attached to / registered with specific domain names. You need to request and let them know you want to use on "localhost".
The alternative is (if you can) to update your development machine's host file with the registered domain name such that the domain name (e.g. example.com) points to your local machine (127.0.0.1). That will require you to also set up a site on your web server.
Hope that helps.
If you own a domain you can refer a subdomain to your local computer IP.
Then you install Sendy with this domain.
From Sendy forum: https://sendy.co/forum/discussion/2866/development-licences#Item_2
Related
I decided to reinstall Sitecore 8 instance via wizard, I have removed instance and install a new one with the same name XYZ.
but after reinstall it I am getting an error in browser - ERR_NAME_NOT_RESOLVED
I checked IIS binding, I checked hosts file, reset DNS, restart PC and etc I still get this error in any browsers.
How I can fix it? What is the issue?
I have found solution https://support.microsoft.com/en-us/kb/2823477 but I can't understend how sitecore installer can change it.
Generally, the process of site resolution goes in the following consequence:
DNS - find ip address by the hostname (from request header)
Access IIS with that IP (and port if not default 80)
IIS checks bindings by hostname from header and serves corresponding website.
Website being resolved has (merged) web.config in root folder. It has node with all sites served by current Sitecore instance, being listed. Order does matter! First successful match (by hostname or port or default) works it out.
Site being found on previous step has startItem property which is your Sitecore item served by dafault.
Please go and carefully check all those steps to see where it breaks. Also I have previously write a blog post, you may find it helpful with more details on that:
http://blog.martinmiles.net/post/how-websites-are-resolved-with-sitecore
Do any sites work with a Local name configured in 'hosts'?
You may need to disable the Loopback Check in your tcpip stack. Windows uses this as a countermeasure for man in the middle attacks by default on many systems. A registry change is needed to allow a machine to refer to itself using a name that is not its own Hostname. Sorry, but I can't remember the actual key.
I recently started a project of building a server at home and trying to host a website on it. I have almost everything setup and working correctly but only have one issue, I can't figure out how to use my domain with it. I've been searching the internet for a few days and everything I come across isn't very informative on how to do it. I'm very new to hosting my own servers and would love any help. Thanks in advanced.
I should also mention that I'm using Windows Server 2012 R2 and IIS 8. The computer has a static IP as well.
Not sure what you mean by use my domain but I am guessing if you go to the url it is not loading you site? If that is the case, have you registered you bomain with a provider (godaddy, namecheep, etc)? After that make sure your router is forwarding the ports needed to your computer. Lastly make sure that those ports are open on your firewall. Things to help debug issues is can you ping your domain and get your static IP, if not the issue is with your domain registration. If it tries to load the site and doesn't but the IP is good then the issue is between the provider and you computer more than likely.
I have IIS installed with asp.net 4.0. I've managed to get my site showing on a static ip address and port forwarding is set up on my router but for some reason the site is still only showing locally and not on only external networks. Is there any obvious causes for this. I'm pretty new to IIS and have looked for hours so far to try and find out why I can access my site externally.
Currently the page just times out on external networks.
Any help would be great, thanks in advance.
I worked out it was because I was pointing from my domain to the local IP and not Public IP, worked fine once I changed this.
This sounds like an issue with your network configuration rather than an IIS issue.
Here's a few things to try:
Can you access the website from another machine on the same network?
Is port 80 open on your router?
Verify that your ISP is not blocking inbound requests on port 80
I have a test environment where I want to have IIS installed on 2 servers, in such a way that they host a website tied to a single IP balanced via NLB and routed via ARR. I have the two servers with IIS 7.5 installed now.
What I am looking to do is:
Host a site inside of IIS using UNC (I can already host a sample site inside of wwwroot locally)
Install NLB as a cluster for both servers
Install ARR and add a ServerFarm in IIS for both servers
Can anyone tell me if any of this is possible? I have looked into various pages on ServerFault, as well as here on stackoverflow, on IIS.net, on other forums, without success. I just need a basic website that I can get hosted on an internal fileshare via UNC path.
Any assistance with this would be greatly appreciated.
Thank you,
G
Yes, this is absolutely possible, in fact there are great tutorials on doing just that:
http://www.iis.net/learn/extensions/configuring-application-request-routing-(arr)/achieving-high-availability-and-scalability-arr-and-nlb
http://www.iis.net/learn/extensions/configuring-application-request-routing-(arr)/configure-3-tier-deployment-architecture-using-application-request-routing
Guys I have build a website and testing it on localhost using LAMP on ubuntu. Now i want to publish this website on my local network. how do I do it.? Please help. Thanks.
Install a webserver somewhere on your local network (this could be the one you have been using for testing if you don't want to have separate development and live environments … although that usually isn't a good idea).
Publish the site to that webserver (in the same way you are doing for your development server).
Give out the URL to the site