Plesk Webserver - New domain redirects to server IP rather than index.html - plesk

I'm running Plesk 12.0.18 on Ubuntu 12.04.5 and have a problem with a recently added domain.
The domain was added to plesk for a new website and has its own directory (httpdocs/goodsnap). When I visit the domain http://goodsnap.co.uk it redirects to the default domain on the server IP rather than opening the index.html file within httpdocs/goodsnap.
I can open the index file manually by going to http://goodsnap.co.uk/index.html and also get into WP by going to http://goodsnap.co.uk/wordpress
Can anyone advise how to rectify this? I have tried setting a redirect to the wordpress subdirectory by placing a .htaccess in httpdocs/goodsnap but it makes no difference.
Many Thanks
Tom

Related

plesk use specific directory as root for website

I got used to have all my websites in /var/www so no matter which domain, each subdomain has its document root located in /var/www/
Plesk is trying to force me to use /var/www/vhosts/domain/ and I did not find a way to tell Plesk to just put everything into /var/www.
I don't want a whole new structure, I want to migrate my existing websites from my old server (without Plesk) to my new server running Plesk 17.8
Edit: Feel free to answer this question for future reference but I won't need it as I realized that no sane person would use Plesk. Server will be reinstalled.
This may help you:
In Plesk for Linux, transvhosts.pl utility can be used to change the location for all virtual hosts:
# /usr/local/psa/bin/transvhosts.pl --help
In the following example, the location is changed to /home directory:
# /usr/local/psa/bin/transvhosts.pl --dest-dir /home --correct-scripts
Note, that currently Plesk Onyx with SELinux enabled does not support custom vhosts directory.

Not loaded wordpress database on the live server

I move my site from localhost to live host server:
1. upload my wordpress website source to server
2. create a database and import localhost database
3. change 'home' and 'siteurl' option to domain name
4. copatible config.php with new live database information
but not load database and show /wp-admin/install.php page!
I try with Duplicator plugin and result is same.
I create another localhost website with this things but work correct!
enter image description here
This generally happens if .htaccess file is missing when you uploaded WordPress to live server. Hiddne file may have been missed when you copied your web pages to server.
Permalinks is another root cause of the issue.
Please check if you are able to browse your admin area directly: http://domain.com/wp-login.php. If so, login and go to permalinks settings. Do NOT make any change and click on Save directly.
This will create your .htaccess file and check your site again.

How do I configure Bolt CMS on an subdomain correctly?

I currently have a working Bolt installation on my main domain (i.e. example.com). But I also wanted a subdomain (i.e. blog.example.com).
I created it, but when I uploaded Bolt to it, but when I tried to access it I only got 404 errors.
I tried copying the Bolt installation from the main domain, then only the main page works, but when I try to access the CMS I get a 404 error. Also if I try to access other pages (i.e. blog.example.com/images) I get a 404.
I tried to change the RewriteBase in the .htaccess to all possible things, but no result.
Also if I do it on another hosting company it is just working, does anyone have a suggestion?
Thanks in advance!
if it is working at another hosting company, maybe that is something non-bolt related issue.
I assume that both of them Apache, so after checking file access rights then I would check apache log.
I had the exact same issue and found out that mod_rewrite was disabled on my sub domain.

How can I add an additional site to my VPS server?

I have a VPS hosting service. First of all, I installed bind9 and everything that my main website works just fine. Now, I bought another domain and set its nameserver address&ip to my website ones.
I added a configuration file of that site like '/etc/apache2/sites-available/www.example.com' and I did 'a2ensite www.example.com' to enable the website to apache2. After one, when I reloaded my server, I see '000default' and 'www.example.com' in my '/etc/apache2/sites-enabled/' directory.
I have thought I am done with settings, but I still cannot connect to the domain example.com. I think I have read it somewhere that I have to set up 'zone' thing which I did when I was setting dns.
For example,
zone "example.com" IN {
type master;
file "example.zone";
allow-update { none; };
};
Is this correct? If so, what are the things that I need to do afteron?
I can see a very descriptive answer here It includes everything from hosting multiple domains to even getting sub domains up on the same VPS.

DotNetNuke error

I hosted one DotNetNUke Application to my production server, and locally it works perfectly. But, when browsing it redirects to the error page.
How do I set the default.aspx as my application default page? I am getting the error as below:
DotNetNuke Error
--------------------------------------------------------------------------------
Windows Vista
Return to Site
Can anyone can help me, please? Will be appreciated.
UPDATE:
Hi, I changed the Path in the PortalAlias table to the server url and default.aspx as the starting page, but it displays the error.aspx as default page.
Please help me resolve this problem..
So, the application works perfectly locally, but not when you put it on the server. Is that correct?
Make sure that your portal alias is valid. If the site is hosted at
http://www.mysite.com
then www.mysite.com needs to be listed in the PortalAlias table
If you open that table in SQL Mgmt Studio, you'll probably see an entry attaching the portal to your local DotNetNuke folder (ie. localhost). Just add a new entry that points to the same PortalID, but with the correct URL for your production server.
Assuming your DNN installation is at "mysite.com", if you navigate to
http://www.mysite.com/default.aspx
do you still get the error page? If so is any error listed?
I was able to fix the issue (for me) by taking the web.config file from a working site with the same version of DotNetNuke and modifying it to have to correct machine key and connection strings. This is my last resort something is really strange procedure.

Resources