Jump to content

pab49162

Members
  • Posts

    5
  • Joined

  • Last visited

Profile Information

  • Gender
    Male

pab49162's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Thank you for the reply as the information you provided fixed my problem! In case anyone else has the same question, you can find out which version of PHP you are using in the MultiPHP Manager under the Software category on the cPanel home page. In my case, I was inheriting the system default PHP version which is ea-php56. So in the .htaccess file, I added the following directive: AddType application/x-httpd-ea-php56 .html Once I did this and saved the file, the server did processed the embedded PHP script. Thanks again - Paul
  2. With the demise of the Stevie server, I now have an account on the Tommy server and am trying to get a website back up and running. I am having a problem getting the server to parse PHP scripts embedded within HTML files having an .html extension. On Stevie, I used the following .htaccess directive to set up html files so they were executed like php files: AddHandler application/x-httpd-php5 .html Unfortunately, this directive does not seem to work on Tommy as the embedded PHP script is basically ignored. Any info on what I need to do to resolve this problem would be greatly appreciated. Thanks - Paul
  3. Just a quick follow-up on my previous post ... I was able to successfully create an add-on domain after temporarily changing the DNS record to the HelioHost nameservers for the add-on domain. Once the add-on process completed (took about 2 minutes), I changed the DNS record back to the original GoDaddy’s name servers and add A records for the add-on domain. After creating the add-on domain, I also created a couple sub-domains for the add-on domain. The sub-domain creating process worked without me having to temporarily change back to the HelioHost nameservers. To access the sub-domain, I simply created a new A record that subdomain on GoDaddy. Hopefully, this information will be helpful to other users trying to do the same thing ...
  4. Hi – thanks for the quick response to my problem and I understand the proposed solution. I already have the IP address of the account and am pretty familiar creating/modifying A records. My long-term plan is to add a couple more existing domains as add-ons once I get through the process of adding the first one. So the solution to change the main domain will work for the first domain, but I will then face the same issue with the subsequence add-ons. After reading a couple other posts, it appears that I can temporarily change the DNS record to your nameservers to add the add-on domain. Then I can change back to the original GoDaddy’s name servers and add A records for any of the add-on domains and sub-domains. I will give this workaround a shot and see how if it solves this issue. Thanks again for your help … Paul
  5. Hi – I am trying to create an addon domain for an existing website and have run into an issue. After entering the necessary info on the CPanel Addon Domains page, I get the following error message: Error from park wrapper: Using nameservers with the following IPs: 208.109.255.42,216.69.185.42 Sorry, the domain is already pointed to an IP address that does not appear to use DNS servers associated with this server. Please transfer the domain to this servers nameservers or have your administrator add one of its nameservers to /etc/ips.remotedns and make the proper A entries on that remote nameserver. I already realize that the domain in question (pabwebsolutions.com) does not currently point to one of your web servers. As this is an existing site, my plan was create the add-on domain, create a subdomain for that site, and then replicate the website on that new subdomain. That way, I could confirm things were working correctly before officially moving the main website. This domain already has multiple subdomains on multiple web hosts and I control where they are hosted via A records on the registrar (GoDaddy). I would prefer to continue using GoDaddy’s name servers for this domain and not change to your name servers. (As an experiment, I did add your name servers as NS records on the remote chance this would satisfy your automated system check – it didn’t.) Checking previous posts, I found an individual with a very similar problem: http://www.helionet....n-to-heliohost/ The following entry summarizes that resolution - “The system prevents domains that aren't pointed at our servers from being added for security reasons. An admin can override this protection though and add the domain for you.” Please advise if there is an alternate approach to add “pabwebsolutions.com” as an add-on domain while still retaining GoDaddy nameservers. Otherwise, I would request an admin add “pabwebsolutions.com” as an add-on domain to my main domain pab49162.heliohost.org. Thanks in advance for your assistance - Paul
×
×
  • Create New...