I am going through the kentico11 developer essential training and the first requirement is to setup a kentico11 site. I followed the instructions and when done this is all I get
Error Message:
Either the website is stopped or the requested domain name is not configured for any website: http://localhost/Kentico11/CMSMessages/invalidwebsite.aspx
If you're an administrator of this site, you need to go to Sites and make sure the following domain name is configured either in the site properties or a domain alias of a running web site: localhost
How do I proceed? I applied the license in the training package
Once you have added the license for the domain you are using to run the site, you need to add the domain to the Site domain name field in the Sites application in Kentico.
Open the Sites application.
Edit (pencil icon) the site.
Type the domain into the Site domain name property on the General tab - since you are running the site under localhost, simply add localhost to the field.
Click Save.
Now when you visit the homepage, the error message should no longer appear.
Documentation reference:
https://docs.xperience.io/k11/configuring-kentico/managing-sites/setting-domain-names-for-sites
Related
My problem is similar to this one. But I need to make one step further.
I whant to publish my website webview on google play. Google Play have rejected my submission but after I send them a email they respond and said that they will allow app publication if I send them pdf with distribution agreement, authorization contract, website domain information or something like that prooving my website ownership. My website hosted on azure. I have domain name like xxxxx.azurewebsites.net. Please help me to understand how can I make pdf document that prooves my website owership.
Will be very greatfull for help!
First, about how to verify your Azure Website ownership, you can refer to these Google documents as below.
Handling Android App Links
Secure and specific: Android App Links use HTTP URLs that link to a website domain you own, so no other app can use your links. One of the requirements for Android App Links is that you verify ownership of your domain through one of our website association methods.
and
Add verification for your deep links: Configure your app to request verification of app links. Then, publish a Digital Asset Links JSON file on your websites to verify ownership through Google Search Console. Learn more in Verify App Links.
Verify Android App Links
To verify ownership of both your app and your website, the following steps are required:
Request automatic app link verification in your manifest. This signals to the Android system that it should verify your app belongs to the URL domain used in your intent filters.
Declare the relationship between your website and your intent filters by hosting a Digital Asset Links JSON file at the following location:
https://domain.name/.well-known/assetlinks.json
The section Verify your website of App Indexing on Google Search in Play Console Help introduces the steps
Sign in to your Play Console.
Click All Applications All applications.
Select the application you'd like to verify.
On the left menu, click Development tools > Services & APIs.
Under "App Indexing from Google Search," click Verify website.
Type your website address.
Click Verify.
Go to Google Search Console.
On the left menu, click All Messages.
Open the verification request message (example: "Google Play: Link http://www.yourwebsite.com to android-app://example.com.yourpackage.name").
Click Approve the request.
Review the information and click Approve. Once approved, your app will appear on the
Search Console Home Page for your account. Be sure that your app enables deep links.
If you have a Google Search Console account or not, here is two links of Verify your site ownership of Search Console Help for old and new Search Console will be helpful.
Tip: Only Google Search Console users with "Owner" permissions can view and approve site verification requests. If you don't see your site verification request, make sure you're signed in using an account with "Owner" permissions.
Second, the xxxx.azurewebsits.net is just a subdomain of azurewebsites.net which be registed by Azure and you can lookup the related info via https://www.whois.net/ as the figure below, so it's not belong to you.
Therefore, you need to register a domain name like abc.com in the Domain Name Registrar like GoDaddy or others, and add a CNAME record with it into DNS server like Azure DNS, then to follow the above steps required by Google to verify your website ownership and collect the necessary information to make a PDF document to send to Google.
I am in kind of strange situation and cannot figure out whats the problem.
I have a Custom Page named /ISV/Portal/Portal.aspx and Custom Configuration Path /ISV/CustomConfiguration/Web.config
In Config File i have ServerName, user Login(i.e Administrator), Password to Create Service.
When account form is viewed by Development Manager of CRM the page is diplayed
and working fine, but the Page is not shown to any other Persons including users having Administrator Role
The Following Message is Displayed:
Unable to change domain logon name
You do not have the necessary permissions to change the domain logon name for this user
After surfing the Internet:
I was not able to make my aspx page work successfully.
At last i hosted my webpage as an independent Website:
Hosted separate Asp.net Website
Published my Custom Page in that directory.
Gave access rights to read/write the C:/TempImages
And Changed the IFrame url to my new location.
Now it's working like a charm :)
I just purchased a domain for my blogger blog through google(goDaddy)
Currently, it is pointed to blogger web host.
I'd like to point it to my own web host as well, so i can host files, while not losing my blog stuffs from blogger.
Is this possible? for a domain to have 2 web host?
I'm sorry, i'm really new to these domain and hosting, any help would be appreciated. Thanks!
You can keep your domain on your site and then setup a subdomain-- like blog.YOURDOMAIN.COM-- and point that to your blogger account.
Go to http://www.google.com/a/domainname, replacing domainname with your domain name.
Now you will need to login to your Google account utilizing a username and password you previously created specifically for Google Apps for your domain. If you do not know this information, click 'Can't access your account.'
Once logged in, click the 'Domain Settings' tab.
Click on "Advanced DNS Settings".
You will now see listed your Sign-In Name, Password, and PIN.
Click Sign-In to DNS Console and use the Sign-In Name and Password to login.
You should now be in the Domain Control Center. Click Forward, and then select Forward Subdomain.
In the Add subdomain field, enter the subdomain.
Select http:// or https:// depending on your server settings.
In Forward this subdomain to, enter the URL you want to forward the subdomain to. This will be the URL for your Blogger blog.
To view additional options, click Advanced Options, and then select one of the following:
Forward Only — Specifies the length of time for this forwarding setting. Select one of the following redirect types:
I am permanently forwarding my domain — Redirects to the site you specified in the Forward To field using a "301 Moved Permanently" HTTP response. The HTTP 301 response code tells user-agents (including search engines) the location has permanently moved.
I am only temporarily forwarding my domain — Redirects to the site you specified in the Forward To field using a "302 Found" HTTP response. The HTTP 302 response code tells user-agents (including search engines) that the location has temporarily moved.
Forward with Masking
Title — Displays at the top of the browser window and in search results.
Description — A short description of your website to display in search engine results.
Keyword — A list of comma-separated keywords that describe the content and purpose of your website.
Click OK.
The main domain you just continue to point to the IP of your web host.
We have a SharePoint site which serves as our company site on the internet. Our company has 2 domains ".com" and ".co.uk". SharePoint works fine when you access the site using the ".com" domain. The problem is, when you try to access the site using the ".co.uk" domain, some pages (ones including custom lists, settings pages) do not work properly.
After doing some research, I found out that I needed to add the ".co.uk" domain under Sharepoint access mappings to make it work properly, but when I do that, I am redirected to the ".com" domain. By the way, the".com" domain already exists in the accesss mappings page.
So, what's the best way to configure our Sharepoint site to work for 2 different domains?
In addition to the alternate address mapping create a IIS website for it. This link might not 100% apply to what your using, but you should be able to make ends meet with it.
http://www.isaserver.org/img/upl/spskit/3quickstart/3quickstart.htm#_Toc58577520
I solved the problem today. Here's how:
First I learned how to extend a Sharepoint site using the video: http://technet.microsoft.com/en-us/sharepoint/Video/ff679931.
In SharePoint Central Administration, I extended the default site (SharePoint - 80) for the ".com" domain.
Used "Create a new IIS web site Name" option, used domain name as the name,
Used port 80, domain name as the host header and the default sharepoint path,
Didn't change Authentication and SSL options, allowed anonymous access
Used the ".com" domain in URL and used Internet as the zone.
After extending a new IIS site was created. In Internet Manager, I clicked "Edit Bindings" option for the new site. The ".com" domain was already set in bindings. I added the ".co.uk" domain into bindings as well.
In Central Administration > Alternate Access Mappings, I set the ".com" domain URL as the Default zone and the ".co.uk" domain as the Internet zone. This automatically added internal URLs for both domains.
I have a sharepoint site hosted on windows server 2008 r2 and iis7.
the sharepoint site is hosted on port 80.
when I browse the site by typing the IP of the machine I receive a login window asking for credentials to connect the Machine. after providing credentials another login window asks for credentials to connect to the sharepoint site.
my question is that when a user logs in to a sharepoint site he uses the credentials specified in the active directory, so why in my case I recieve the login window twice ?
thanks
I've seen this before but rough guess:
When a SharePoint site has a reference to a resource held inside another site (not necessarily SharePoint).
e.g.
http://mysharepoint/
contains perhaps an image with the url http://someothersite/images/someimage.gif.
Not necessarily an image, it would be any resource.
Best way to check could be to view source and check to see if there are any urls pointing to outside the site.
Also check for urls starting with https: .
Hope this helps.
Another thought:
Since you're accessing the site through the IP address, maybe its treating your IP address site (http://192.168.1.1) seperately to the actual host headed sharepoint site (http://actualsharepointsite). Therefore the first authentication prompt is for the IP address host headed site and the second is for the actual host header of the sharepoint site.
To eliminate this, I would try (if you have access to these areas):
a) Logon to the actual box, and browse the site on the actual server using its proper host header (might need host file entry and proxy bypass setup depending on your environment). See how many times you're prompted for login details.
or b) In Central Admin, try to setup Alternate Access Mapping from the IP Address url to the actual host headed url.
Sorry if this doesn't help..