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.
Related
I am finalizing my Joomla-site with a Siteground host and encounter the following problem: my site shows the IP-adress instead of the url. Although I type in the url (www.nooitmeerfile.be by the way), it shows the IP-adress.
Could someone please give me a step-by-step explanation on how to fix this? I happen to find a lot of fragmented answers cluttered around the web. I am a novice user, and I'm stuck :-)
Thanks!
Possible steps to debug your issue:
Check configuration.php public $live_site = ''; and try to add your
domain (without trailing slash).
Check if .htaccess file is not altered and try to download and use a fresh copy.
Check if you are using 3rd party sef components / plugins and try to disable them.
Clear your joomla and browser cache.
Contact your hosting provider if something in your hosting is misconfigured.
Hope this helps
I have one knowingly good site. It works as expected. I copied all the files from that one directory to a new directory. I created a new website with the correct host header and pointed it to the new directory. When you browse to the new site you get a 404 error.
I have checked the file permissions. I have even made the two sites share the same app pool.
Any suggestions would be helpful.
If you look in /App_Data/Logs you can see the error message. As it turned out for me, it was because I was trying to run the same "tenant" twice on the same server.
I have a website where customers can download msi files. Over time, I retire older version and drop them from my site.
I've noticed that a number of users are following links to the older file paths. When the do, they're seeing the following:
Not Found
The requested URL /files/VBADiff/VBADiff_Professional_Setup_2_0.msi was not found on this server.
Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.
I would like to either display my custom 404 message or redirect them to the correct download path. Unfortunately I can't figure out how to do this - I'm a bit surprised that visitors aren't already seeing my 404 message. Can anyone help?
Edit: I'm using version 1.5.11 of Joomla.
File downloads, particularly direct links from an outside referrer do not instantiate the Joomla framework so nothing in Joomla is going to help your problem. Depending on the URLs you are using to get to the files, you will have to fix this issue with either a typical 301 redirect for URLs without query strings or mod_rewrite for those with.
You can use a redirect plugin for joomla 1.5 which also protocalls 404 accesses. I like this one: http://extensions.joomla.org/extensions/site-management/url-redirection/14676
I am trying to deploy my locahost CakePHP website to a subdomain. I am able to view the website but it is not working correctly when I try to login or register.
It does not show me any validation error nor does it allow me to login or register and it is landing on the below URL:
subdomain.example.com/webroot/index.php?url=users/login
where it should be something like:
subdomain.example.com/users/login
I am using Go Daddy shared hosting.
The older settings defined at http://bakery.cakephp.org/articles/cguyer/2009/10/18/mod-rewrite-on-godaddy-shared-hosting has solved the issue.
Thank you every one for your help.
This sounds (and looks) like an Apache rewrite issue. There are a couple of things you need to look at:
Check to make sure the .htaccess files are were they are expected. You should have one in the app directory and another in the webroot directory. Sometimes when we compress and/or transfer files to the webserver, the .htaccess files get left behind.
Make sure that the server you are running the site on has rewrite turned on. This may require that you call support at Go Daddy. But my experience is they are always willing to help.
Good luck!
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.