If you are trying to make your custom domain published blog work, see my guide Troubleshooting Your Custom Domain Problems.
If you want to know how to setup a custom domain properly, from the beginning - and avoid the need for Troubleshooting - read Setting Up DNS Addresses For Custom Domains. Avoid the most basic mistakes made - read The Simplicity Of A Custom Domain Setup.
If you just setup your custom domain - and want to minimise the effects of the URL change upon your search engine relationships - read Managing The Migration.
If you're just browsing, then read on - but get a good cup of coffee first. And welcome, to Nitecruzr Dot Net.
Showing posts with label Troubleshooting. Show all posts
Showing posts with label Troubleshooting. Show all posts
Blogger Magic - Using An HTTP Trace
An HTTP trace is a very useful tool, for diagnosing and documenting connectivity issues, and many other blog problems.
I use the Rex Swain HTTP Viewer, for this purpose. HTTP Viewer lets you package a given display, in the URL, so you can give simple instructions (accompanied by an unavoidably complicated link):
I use the Rex Swain HTTP Viewer, for diagnosing and documenting custom domain, malware, spam classification, and other connectivity issues.
Start by verifying URLs involved.
Whenever possible, make a screen print, and a text copy, of the Blogger dashboard Publishing wizard, at Settings - Basic.
Here's a live example, of HTTP Viewer use.
Start from http://www.rexswain.com/httpview.html.
Note, HTTP Viewer only works in HTTP mode. SSL is not supported. Fortunately, right now, the automatic "http:" to "https:" Blogger redirect, which is not optional, does not affect HTTP Viewer.
Add the URL of the blog, and click on "Submit".
This generates a lot of text. I'm not going to explain all of it, in this post.
Since Blogger blogs have no post limit, I'll have more posts, later, that will involve HTTP Viewer displays.
But here's the second page, of the above display.
And here is the typical excerpt, that I will make, and display.
This is an example of a notorious "500 Internal Server Error" - which right now is plaguing various blog owners who have corrupt templates. This is what we see with many blogs, when people report various bX codes, when using several Blogger dashboard pages.
Here's a second live example.
Here, we have an HTTP trace from this blog, http://blogging.nitecruzr.net/.
And, my typical display - which you might see, as an "HTTP trace excerpt", in a custom domain connectivity diagnosis.
The latter connectivity diagnosis might be a part of my 12 link affinity / differential connectivity test.
My trace excerpts include details which I, personally, decided are most useful for me. You may find additional - or less - details to be useful, for you.
Here, we see just two examples, of my HTTP traces. There are an infinity of possibilities.
An online HTTP trace is a useful diagnostic tool, when diagnosing and identifying many different #Blogger problems. Custom domain, malware, spam classification, and other connectivity issues may be diagnosed and documented.
I use the Rex Swain HTTP Viewer, for this purpose. HTTP Viewer lets you package a given display, in the URL, so you can give simple instructions (accompanied by an unavoidably complicated link):
Click on the link:And when the link is clicked, the necessary HTTP trace is displayed. There is no need to provide instructions how to actually enter the necessary values, on the HTTP Viewer home page, to generate the necessary display.http://www.rexswain.com/cgi-bin/httpview.cgi?url=http://klarfamilylife.blogspot.com&uag=Mozilla/5.0+(X11%3B+CrOS+armv7l+7834.70.0)+AppleWebKit/537.36+(KHTML,+like+Gecko)+Chrome/49.0.2623.112+Safari/537.36&ref=http://www.rexswain.com/httpview.html&aen=&req=GET&ver=1.1&fmt=AUTO
I use the Rex Swain HTTP Viewer, for diagnosing and documenting custom domain, malware, spam classification, and other connectivity issues.
Start by verifying URLs involved.
Whenever possible, make a screen print, and a text copy, of the Blogger dashboard Publishing wizard, at Settings - Basic.
Here's a live example, of HTTP Viewer use.
http://www.rexswain.com/cgi-bin/httpview.cgi?url=http://klarfamilylife.blogspot.com&uag=Mozilla/5.0+(X11%3B+CrOS+armv7l+7834.70.0)+AppleWebKit/537.36+(KHTML,+like+Gecko)+Chrome/49.0.2623.112+Safari/537.36&ref=http://www.rexswain.com/httpview.html&aen=&req=GET&ver=1.1&fmt=AUTO
Start from http://www.rexswain.com/httpview.html.
Note, HTTP Viewer only works in HTTP mode. SSL is not supported. Fortunately, right now, the automatic "http:" to "https:" Blogger redirect, which is not optional, does not affect HTTP Viewer.
Add the URL of the blog, and click on "Submit".
This generates a lot of text. I'm not going to explain all of it, in this post.
Since Blogger blogs have no post limit, I'll have more posts, later, that will involve HTTP Viewer displays.
But here's the second page, of the above display.
And here is the typical excerpt, that I will make, and display.
http://www.rexswain.com/cgi-bin/httpview.cgi?url=http://klarfamilylife.blogspot.com&uag=Mozilla/5.0+(X11%3B+CrOS+armv7l+7834.70.0)+AppleWebKit/537.36+(KHTML,+like+Gecko)+Chrome/49.0.2623.112+Safari/537.36&ref=http://www.rexswain.com/httpview.html&aen=&req=GET&ver=1.1&fmt=AUTO
Sending request:
GET / HTTP/1.1
Host: klarfamilylife.blogspot.com
User-Agent: Mozilla/5.0 (X11; CrOS armv7l 7834.70.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.112 Safari/537.36
Referer: http://www.rexswain.com/httpview.html
Connection: close
• Finding host IP address...
• Host IP address = 172.217.0.1
• Finding TCP protocol...
• Binding to local socket...
• Connecting to host...
• Sending request...
• Waiting for response...
Receiving Header:
HTTP/1.1·500·Internal·Server·Error(CR)(LF)
This is an example of a notorious "500 Internal Server Error" - which right now is plaguing various blog owners who have corrupt templates. This is what we see with many blogs, when people report various bX codes, when using several Blogger dashboard pages.
- Template.
- Template - "Customize" (aka "Blogger Template Designer").
- Template - "Edit HTML" (aka "Blogger Template Editor").
Here's a second live example.
http://www.rexswain.com/cgi-bin/httpview.cgi?url=http://blogging.nitecruzr.net/&uag=Mozilla/5.0+(X11%3B+CrOS+armv7l+7834.70.0)+AppleWebKit/537.36+(KHTML,+like+Gecko)+Chrome/49.0.2623.112+Safari/537.36&ref=http://www.rexswain.com/httpview.html&aen=&req=GET&ver=1.1&fmt=AUTO
Here, we have an HTTP trace from this blog, http://blogging.nitecruzr.net/.
And, my typical display - which you might see, as an "HTTP trace excerpt", in a custom domain connectivity diagnosis.
http://www.rexswain.com/cgi-bin/httpview.cgi?url=http://blogging.nitecruzr.net/&uag=Mozilla/5.0+(X11%3B+CrOS+armv7l+7834.70.0)+AppleWebKit/537.36+(KHTML,+like+Gecko)+Chrome/49.0.2623.112+Safari/537.36&ref=http://www.rexswain.com/httpview.html&aen=&req=GET&ver=1.1&fmt=AUTO
Sending request:
GET / HTTP/1.1
Host: blogging.nitecruzr.net
User-Agent: Mozilla/5.0 (X11; CrOS armv7l 7834.70.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.112 Safari/537.36
Referer: http://www.rexswain.com/httpview.html
Connection: close
• Finding host IP address...
• Host IP address = 74.125.25.121
• Finding TCP protocol...
• Binding to local socket...
• Connecting to host...
• Sending request...
• Waiting for response...
Receiving Header:
HTTP/1.1·200·OK(CR)(LF)
<meta·content='blogger'·name='generator'/>(LF)
<link·href='http://blogging.nitecruzr.net/favicon.ico'·rel='icon'·type='image/x-icon'/>(LF)
<link·href='http://blogging.nitecruzr.net/'·rel='canonical'/>(LF)
<link·rel="alternate"·type="application/atom+xml"·title="The·Real·Blogger·Status·-·Atom"·href="http://blogging.nitecruzr.net/feeds/posts/default"·/>(LF)
<link·rel="alternate"·type="application/rss+xml"·title="The·Real·Blogger·Status·-·RSS"·href="http://blogging.nitecruzr.net/feeds/posts/default?alt=rss"·/>(LF)
<link·rel="service.post"·type="application/atom+xml"·title="The·Real·Blogger·Status·-·Atom"·href="https://www.blogger.com/feeds/24069595/posts/default"·/>(LF)
The latter connectivity diagnosis might be a part of my 12 link affinity / differential connectivity test.
My trace excerpts include details which I, personally, decided are most useful for me. You may find additional - or less - details to be useful, for you.
Here, we see just two examples, of my HTTP traces. There are an infinity of possibilities.
An online HTTP trace is a useful diagnostic tool, when diagnosing and identifying many different #Blogger problems. Custom domain, malware, spam classification, and other connectivity issues may be diagnosed and documented.
How To Unmap Google Sites To Solve "Another blog or Google Site is already using this address."
The literal cause of the error "Another blog or Google Site is already using this address." is that the Google Sites service is mapped to the address in question, in the Google domain services mapping database.
Some help articles published on the Internet imply that Sites mappings are the only cause of this error. This misconception creates some of the confusion associated with the error. Sites is not the only service in the services mapping database - but it is the only service with web address mappings.
The Sites service contains both service address, and web address, mappings - and both mappings can cause this problem. This oddity creates complexity, and makes a linear check list impossible, when using Google Apps to clear the error - as well as diagnosing the error, in a typical dialogue in Blogger Help Forum: Something Is Broken.
When the Sites service is suspected as the cause of "Another blog or Google Site is already using this address.", one must check both the Service Address Mapping, and the Web Address Mappings, in the Sites service.
Note that the presence of the mappings is not directly affected by the presence of the service wizards, on the desktop of the Google Apps account which you are using. Neither deleting the Apps account, nor uninstalling a given service wizard from the desktop, will immediately reset the mappings for that service, from the database.
If not present on the desktop, the Sites service must be first installed and activated, using the dashboard "Get more apps and services" link.
The Sites service address mapping, like all other services, can be examined and reset using the CustomURL form in Google Apps, as well as "Change URL" in the "General" tab, in the Sites Settings menu. The web address mappings can only be examined and reset using the "Web Address Mapping" tab, in the Sites Settings menu.
If a Sites mapping is not the cause of your problem, Sites won't have a mapped address, in "Web Address Mapping". You will then need to check other settings, in Control Panel / Google Apps.
A Sites service address mapping, like other service address mappings, can sometimes be diagnosed in a simple "302 Moved Temporarily" redirect, in a typical HTTP trace.
A Sites web address mapping is not always so easy to diagnose - and may be the reason behind the fact that some HTTP traces end with the blog owner reporting "Another blog or Google Site is already using this address.", and an HTTP trace simply showing the generic 404 Not Found.
A Sites "Web Address Mapping" can include an address which is mapped outside Google Apps. This creates a mapping which can't be managed using Google Apps.
Some help articles published on the Internet imply that Sites mappings are the only cause of this error. This misconception creates some of the confusion associated with the error. Sites is not the only service in the services mapping database - but it is the only service with web address mappings.
The Sites service contains both service address, and web address, mappings - and both mappings can cause this problem. This oddity creates complexity, and makes a linear check list impossible, when using Google Apps to clear the error - as well as diagnosing the error, in a typical dialogue in Blogger Help Forum: Something Is Broken.
When the Sites service is suspected as the cause of "Another blog or Google Site is already using this address.", one must check both the Service Address Mapping, and the Web Address Mappings, in the Sites service.
Note that the presence of the mappings is not directly affected by the presence of the service wizards, on the desktop of the Google Apps account which you are using. Neither deleting the Apps account, nor uninstalling a given service wizard from the desktop, will immediately reset the mappings for that service, from the database.
If not present on the desktop, the Sites service must be first installed and activated, using the dashboard "Get more apps and services" link.
The Sites service address mapping, like all other services, can be examined and reset using the CustomURL form in Google Apps, as well as "Change URL" in the "General" tab, in the Sites Settings menu. The web address mappings can only be examined and reset using the "Web Address Mapping" tab, in the Sites Settings menu.
- Select the "Web Address Mapping" tab, in the Sites Settings menu.
- Select all addresses mapped, and click on "Delete Mapping(s)".
- Click on "Yes" in the "Are you sure" popup.
If a Sites mapping is not the cause of your problem, Sites won't have a mapped address, in "Web Address Mapping". You will then need to check other settings, in Control Panel / Google Apps.
A Sites service address mapping, like other service address mappings, can sometimes be diagnosed in a simple "302 Moved Temporarily" redirect, in a typical HTTP trace.
Sending request:
GET / HTTP/1.1
Host: www.letthykingdomcome.com
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:18.0)
Gecko/20100101 Firefox/18.0
Referer: http://www.rexswain.com/httpview.html
Connection: close
• Finding host IP address...
• Host IP address = 74.125.129.121
• Finding TCP protocol...
• Binding to local socket...
• Connecting to host...
• Sending request...
• Waiting for response...
Receiving Header:
HTTP/1.1·302·Moved·Temporarily(CR)(LF)
Content-Type:·text/html;·charset=UTF-8(CR)(LF)
Location:·http://sites.google.com/a/letthykingdomcome.com/
sites/system/app/pages/meta/domainWelcome(CR)(LF)
A Sites web address mapping is not always so easy to diagnose - and may be the reason behind the fact that some HTTP traces end with the blog owner reporting "Another blog or Google Site is already using this address.", and an HTTP trace simply showing the generic 404 Not Found.
Sending request:
GET / HTTP/1.1
Host: www.markhamdesign.co.uk
User-Agent: Mozilla/5.0
(Windows NT 5.1; rv:19.0) Gecko/20100101 Firefox/19.0
Referer: http://www.rexswain.com/httpview.html
Connection: close
• Finding host IP address...
• Host IP address = 216.239.32.21
• Finding TCP protocol...
• Binding to local socket...
• Connecting to host...
• Sending request...
• Waiting for response...
Receiving Header:
HTTP/1.1·404·Not·Found(CR)(LF)
A Sites "Web Address Mapping" can include an address which is mapped outside Google Apps. This creates a mapping which can't be managed using Google Apps.
If you own a domain and have access to change the CNAME record, you can map any site created in Google Sites outside of Google Apps (for example, sites.google.com/site) to a custom URL
Sending request:A Sites mapping won't always be present - but when it is, it's not difficult to solve - as long as you can access Google Apps aka "Control Panel".
GET / HTTP/1.1
Host: www.medtechpedia.com
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:19.0) Gecko/20100101 Firefox/19.0
Referer: http://www.rexswain.com/httpview.html
Connection: close
• Finding host IP address...
• Host IP address = 74.125.129.121
• Finding TCP protocol...
• Binding to local socket...
• Connecting to host...
• Sending request...
• Waiting for response...
Receiving Header:
HTTP/1.1·200·OK(CR)(LF)
<body·xmlns="http://www.google.com/ns/jotspot"·id="body"·class="·en············">(LF)
<script·src="//www.gstatic.com/caja/5246m/caja.js">·</script>(LF)
<script·src="http://www.gstatic.com/sites/p/926884/system/js/jot_caja.js">·</script>(LF)
<div·id="sites-page-toolbar"·class="sites-header-divider">(LF)
<div·xmlns="http://www.w3.org/1999/xhtml"·id="sites-status"·class="sites-status"·style="display:none;"><div·id="sites-notice"·class="sites-notice"·role="status"·aria-live="assertive">·</div></div>(LF)
</div>(LF)
<div·id="sites-chrome-everything-scrollbar">(LF)
<div·id="sites-chrome-everything">(LF)
<div·id="sites-chrome-page-wrapper"·style="direction:·ltr">(LF)
<div·id="sites-chrome-page-wrapper-inside">(LF)
<div·xmlns="http://www.w3.org/1999/xhtml"·id="sites-chrome-header-wrapper"·style="">(LF)
<table·id="sites-chrome-header"·class="sites-layout-hbox"·cellspacing="0"·style="">(LF)
<tr·class="sites-header-primary-row"·id="sites-chrome-userheader">(LF)
<td·id="sites-header-title"·class=""><div·class="sites-header-cell-buffer-wrapper"><h2>
<a·href="http://sites.google.com/site/medtechpedia/"·dir="ltr"·id="sites-chrome-userheader-title">MedTechPedia</a></h2></div></td><td·class="sites-layout-searchbox·"><div·class="sites-header-cell-buffer-wrapper"><form·id="sites-searchbox-form"·action="/system/app/pages/search"><input·type="hidden"·id="sites-searchbox-scope"·name="scope"·value="search-site"·/><input·type="text"·id="jot-ui-searchInput"·name="q"·size="20"·value=""·aria-label="Search·this·site"·autocomplete="off"·/><div·id="sites-searchbox-button-set"·class="goog-inline-block"><div·role="button"·id="sites-searchbox-search-button"·class="goog-inline-block·jfk-button·jfk-button-standard"·tabindex="0">Search·this·site</div></div></form></div></td>(LF)
</tr>(LF)
<tr·class="sites-header-secondary-row"·id="sites-chrome-horizontal-nav">(LF)
<td·colspan="2"·id="sites-chrome-header-horizontal-nav-container">(LF)
<div·class="sites-header-nav"><ul·class="sites-header-nav-container-tabs"><li·class="current"><a·class="sites-navigation-link·current"·href="/home">Home</a></li><li·class="unselected"><a·class="sites-navigation-link·unselected"·href="/introduction-to-medical-technology">Introduction·to·Medical·Technology</a></li></ul><div·style="clear:·both;"></div></div>(LF)
</td>(LF)
</tr>(LF)
</table>·(LF)
</div>·
How To Solve "Another blog or Google Site is already using this address."
Of all of the problems that are typically reported, in Blogger Help Forum: Something Is Broken, surely the most frustrating has to be
One of the reasons for the frustration is that this is not a descriptive error - it's more of a symptom - and this symptom has a number of causes. Since many Blogger blog owners don't understand the principles of problem solving, the solutions for this error may not be obvious.
The monolithic message "Another blog or Google Site is already using this address." is actually a symptom of a number of possible problems.
Some time ago, I identified three categories of problems, which cause the message to be displayed.
Check For A Blog Already Published To The Address
If there is a blog already published to the URL, and you control both blogs, make a simple decision - which blog to publish, to the URL in question. If necessary, a second blog can be published to a different host in the domain, and setup a domain cluster. In some cases, a previous domain owner may have published a blog, which you won't control, to the domain.
Check The DNS Address Setup
Having eliminated or solved the possibility of multiple blogs, check and - if necessary - correct the DNS addresses setup for the domain. There are three DNS address models - with one, asymmetrical, being involved with over 99% of the blogs reported with this problem. There is simply no alternative to "CNAME" forwarding, when publishing a blog to a custom domain.
Check For Service Redirections
With the DNS addresses corrected - and DNS propagation latency allowed for - diagnose the problem using a series of HTTP traces. Here, we'll generally see a number of possible redirections.
When dealing with service redirections, start by establishing access to the Google Apps domain administrator desktop. If the domain was purchased in 2013 or later, you'll have use of a basic function Apps account. You'll use two Apps desktop wizards - "Organization & users" and "Settings".
Named Service Redirection
For a named service redirection:
Database Corruption Or Unknown Service Redirection
If a specific service is not identified in the HTTP traces, check the "Change URLs for multiple services" display, which is accessible from any "Change URL" service wizard.
Just read about the details, take it one step at a time - and allow time to complete the entire task, carefully.
>> Top
Another blog or Google Site is already using this address.or possibly
Key already exists for domain ...
One of the reasons for the frustration is that this is not a descriptive error - it's more of a symptom - and this symptom has a number of causes. Since many Blogger blog owners don't understand the principles of problem solving, the solutions for this error may not be obvious.
The monolithic message "Another blog or Google Site is already using this address." is actually a symptom of a number of possible problems.
Some time ago, I identified three categories of problems, which cause the message to be displayed.
- The URL in question is actually in use, with another blog already published to that domain URL.
- The DNS addresses are improperly setup, and not pointing to the correct Google servers.
- There are broken / duplicate pointers, which affect the domain, in the Google internal database.
Check For A Blog Already Published To The Address
If there is a blog already published to the URL, and you control both blogs, make a simple decision - which blog to publish, to the URL in question. If necessary, a second blog can be published to a different host in the domain, and setup a domain cluster. In some cases, a previous domain owner may have published a blog, which you won't control, to the domain.
Check The DNS Address Setup
Having eliminated or solved the possibility of multiple blogs, check and - if necessary - correct the DNS addresses setup for the domain. There are three DNS address models - with one, asymmetrical, being involved with over 99% of the blogs reported with this problem. There is simply no alternative to "CNAME" forwarding, when publishing a blog to a custom domain.
Check For Service Redirections
With the DNS addresses corrected - and DNS propagation latency allowed for - diagnose the problem using a series of HTTP traces. Here, we'll generally see a number of possible redirections.
- Calendar.
- Drive and Docs.
- Email.
- Sites.
- Start Page.
When dealing with service redirections, start by establishing access to the Google Apps domain administrator desktop. If the domain was purchased in 2013 or later, you'll have use of a basic function Apps account. You'll use two Apps desktop wizards - "Organization & users" and "Settings".
- Use "Organization & users", to install and activate any service.
- Use "Settings" to disable mappings, and to uninstall any service.
Named Service Redirection
For a named service redirection:
- If necessary, install and activate the service.
- Delete the mappings for the service.
- Uninstall the service.
Database Corruption Or Unknown Service Redirection
If a specific service is not identified in the HTTP traces, check the "Change URLs for multiple services" display, which is accessible from any "Change URL" service wizard.
- Select any service, in the "Settings" wizard, and the "Change URL" link for that service.
- Click on "Change URLs for all domain services".
- Examine the "Change URLs for multiple services" display, and select the custom mapping, for any service with the default mapping (top) address selected. If any service entry is changed, click "Continue".
- For each service with mapping which was just changed:
- If necessary, install and activate the service.
- Uninstall the service.
Just read about the details, take it one step at a time - and allow time to complete the entire task, carefully.
>> Top
How To Use Google Apps To Solve "Another blog or Google Site is already using this address."
The Google domain services database lets one or more Blogger blogs, and / or various Google services, be packaged as part of a domain - giving your organisation its own virtual web server.
Google Apps is used to manage this virtual web server, as you install and un install various domain services. Sometimes a domain, newly setup in Google after the domain has been purchased from a registrar, will have one or more addresses unexpectedly mapped to various Google services. This will be inconvenient to the blog owner, who may wish to use a given URL for a Blogger blog.
The most common cause of the error "Another blog or Google Site is already using this address." involves unexpected mappings, in the Google domain database.
When your domain has unwanted mappings, you'll need to use the Google Apps domain administrator desktop, and various utilities there, to remove the mappings and reset the services. To start, you'll need access to the Google Apps desktop for the domain administrator. For domains recently purchased using Blogger or Google wizards, you'll have a limited function domain administrator desktop.
You'll use two Apps desktop wizards - "Organization & users" and "Settings".
Install And Activate Services
Use "Organization & users" - "Services", to activate the various services.
Remove Mappings
Use the Settings wizard, for the service in question - to add and remove address mappings, and to deactivate services. Each different service, listed in Settings, has a different set of menus, and different options.
We currently know of 5 services which can be mapped to a domain, which may interfere with publication of a Blogger blog to a domain address. Any problem service, currently mapped to the default (top) address, will need to be changed to map to the custom (bottom) address.
To remove address mappings for Calendar:
To remove address mappings for Drive and Docs:
To remove address mappings for Email:
To remove address mappings for Sites, some extra effort may be required:
To remove address mappings for Start Page:
The CustomURL Wizard
Besides the multiple Sites mappings (in "Web Address Mapping"), it may be possible to use the "CustomURL" wizard, which will list all active services and current mappings. The CustomURL wizard is accessed from any "Change URL" wizard.
Disable / Uninstall Services After Changing Mapping
If you did change or delete any mappings, whether using CustomURL ("Change URLs for multiple services") or an individual service wizard ("Change URL" / "Web Address Mapping"), the final step is to disable or uninstall each service for which you changed or deleted mappings. If you do intend to use any named service, re install it later - after you get your custom domain working.
To uninstall Calendar, click on "Calendar", then the "General" tab. Click on "Uninstall Calendar", next to "Uninstall service".
To uninstall Drive and Docs, click on "Drive and Docs", then the "General" tab. Click on "Uninstall Drive and Docs", next to "Uninstall service".
To uninstall Email, click on "Email", then the "General Settings" tab. Click on "Uninstall Email", next to "Uninstall service".
To uninstall Sites, click on "Sites", then the "General" tab. Click on "Uninstall Sites", next to "Uninstall service".
To disable Start Page, click on "Start Page", then on "Disable Start Page", next to "Disable service".
Google Apps is used to manage this virtual web server, as you install and un install various domain services. Sometimes a domain, newly setup in Google after the domain has been purchased from a registrar, will have one or more addresses unexpectedly mapped to various Google services. This will be inconvenient to the blog owner, who may wish to use a given URL for a Blogger blog.
The most common cause of the error "Another blog or Google Site is already using this address." involves unexpected mappings, in the Google domain database.
When your domain has unwanted mappings, you'll need to use the Google Apps domain administrator desktop, and various utilities there, to remove the mappings and reset the services. To start, you'll need access to the Google Apps desktop for the domain administrator. For domains recently purchased using Blogger or Google wizards, you'll have a limited function domain administrator desktop.
You'll use two Apps desktop wizards - "Organization & users" and "Settings".
- Use "Organization & users", to install and activate a service.
- Use "Settings" to disable / remove mappings, and to disable / uninstall a service.
Install And Activate Services
Use "Organization & users" - "Services", to activate the various services.
- To install a service, click on "Dashboard", find "Common tasks" at the bottom left, and click on "Get more apps and services". Click on "Add it now", for the needed service.
- To activate a service, go to "Organization & users" - "Services", and look under "Core Google Services" or "Additional Services", for the service in question - and click on the coloured toggle switch as necessary. Then click on "Save changes".
Remove Mappings
Use the Settings wizard, for the service in question - to add and remove address mappings, and to deactivate services. Each different service, listed in Settings, has a different set of menus, and different options.
We currently know of 5 services which can be mapped to a domain, which may interfere with publication of a Blogger blog to a domain address. Any problem service, currently mapped to the default (top) address, will need to be changed to map to the custom (bottom) address.
- Calendar.
- Drive and Docs.
- Email.
- Sites.
- Start Page.
To remove address mappings for Calendar:
- Click on "Calendar", then the "General" tab, then "Change URL" for "Web address".
- If necessary, select the custom mapping (bottom) address, and click "Continue".
- If you change the Calender mapping, remember to uninstall Calender.
To remove address mappings for Drive and Docs:
- Click on "Drive and Docs", then the "General" tab, then "Change URL" for "Web address".
- If necessary, select the custom mapping (bottom) address, and click "Continue".
- If you change the Drive and Docs mapping, remember to uninstall Drive and Docs.
To remove address mappings for Email:
- Click on "Email", then the "General Settings" tab, then "Change URL" for "Web address".
- If necessary, select the custom mapping (bottom) address, and click "Continue".
- If you change the Email mapping, remember to uninstall Email.
To remove address mappings for Sites, some extra effort may be required:
- Click on "Sites", then the "General" tab, then "Change URL" for "Web address".
- If necessary, select the custom mapping (bottom) address, and click "Continue".
- Select the "Web Address Mapping" tab.
- Select all addresses mapped, and click on "Delete Mapping(s)".
- Some Sites mappings can only be diagnosed, and reset, outside Google Apps.
- If you change any Sites mapping, remember to uninstall Sites.
To remove address mappings for Start Page:
- Click on "Start Page", then "Change URL" for "Web address".
- If necessary, select the custom mapping (bottom) address, and click "Continue".
- If you change the Start Page mapping, remember to uninstall Start Page.
The CustomURL Wizard
Besides the multiple Sites mappings (in "Web Address Mapping"), it may be possible to use the "CustomURL" wizard, which will list all active services and current mappings. The CustomURL wizard is accessed from any "Change URL" wizard.
- Click on "Change URLs for all domain services".
- Examine the "Change URLs for multiple services" display, and disable any references to the default mapping. Select the custom mapping (bottom) address, for any service with the default mapping (top) address selected. If any service entry was changed, click "Continue".
- For each service with mapping which was changed:
- If necessary, install and activate the service.
- Uninstall the service.
Disable / Uninstall Services After Changing Mapping
If you did change or delete any mappings, whether using CustomURL ("Change URLs for multiple services") or an individual service wizard ("Change URL" / "Web Address Mapping"), the final step is to disable or uninstall each service for which you changed or deleted mappings. If you do intend to use any named service, re install it later - after you get your custom domain working.
To uninstall Calendar, click on "Calendar", then the "General" tab. Click on "Uninstall Calendar", next to "Uninstall service".
To uninstall Drive and Docs, click on "Drive and Docs", then the "General" tab. Click on "Uninstall Drive and Docs", next to "Uninstall service".
To uninstall Email, click on "Email", then the "General Settings" tab. Click on "Uninstall Email", next to "Uninstall service".
To uninstall Sites, click on "Sites", then the "General" tab. Click on "Uninstall Sites", next to "Uninstall service".
To disable Start Page, click on "Start Page", then on "Disable Start Page", next to "Disable service".
Posts
![SQL Injection Basics - Union Based [Detailed Tutorial]](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjjQpa2wuMB-m5CXPVf71GUOkfiIOQA8KTyQ-_zfAl0SZa23UBN1QJaO2ZMGRDZlmDJTYf2jJ4ik3Xnj1locc38Yv9l6VMxTWt32s86JtXtLABDn20DRuAcbLPKMb9m2hc6PDmjIjvU-us/s72-c/SQL-Injection-Attack.jpg)
