I'm pulling from non-Joomla SSL proxy experience here. However, I believe it will work.
Configure nginx to send an X-FORWARDED-PROTO header with a value of "https"
proxy_set_header X-Forwarded-Proto https;
Configure Apache to set the HTTPS environment variable to "on":
SetEnvIfNoCase X-Forwarded-Proto https HTTPS=on
Once you have those configured, ...
Do I understand correctly that you want to make your website on your local computer on the Internet?
Apart from the poor uptime that you will experience with this you will need a number of things:
1) Create a tunnel/ server address of your local computer on your Internet Router. This will also mean you will need a fixed IP address on your local network, ...
Leave compression disabled until your site is ready, then try activating the settings on your online server and see ...
I have already taken the "plunge" to nginx, and my findings:
.htaccess rules are one of the main problems, but can be overcome by
"translating" them to nginx configuration instructions (you can do
them by hand, but there are some handy tools on the internet to help
you convert them, like this one: htaccess to nginx converter)
Note that ...
If your admin area works widthout .htaccess its possible your joomla config has rewrite option enable. You can try edit your configuration.php file and change the status directly in configuration file:
$sef_rewrite = '0';
$sef = '0';
$sef_suffix = '0';
I managed to piece together a solution without using .htaccess, though I'm interested in a cleaner solution if somebody has one.
I created a system plugin that really does nothing in the conventional sense, in that it has no methods except _construct ().
In the _construct() method, I simply checked for strings in the URI that were found in the old links ...
Likely Joomla will work without issues even with the php's tmp directory not being set. However, if you get issues, or simply want to get rid of this warning in you Joomla Admin, then you have to define in your php configuration the upload-tmp-dir directive.
Note that setting up the hosting/server environment is not exactly a Joomla question. There is ...
Since this is one of the most common questions around Joomla, I though to share a new extension I came across that deals with it.
Plugin: Direct Alias Pro
For those people that don't want to mess with the extended capabilities of the majority of SEF extensions, this a much simpler plugin, that one of each features is to remove ids from articles, categories ...
If you create a menu item for each of these then the menu item alias is used for the URL instead.
The menu you create these links in doesn't have to be published on your site, it's enough that the menu item exists in menu manager. You can create a new menu called 'dummy links', or whatever you like, and create links to your categories and articles there. ...
The files should be owned by your FTP user, which may be root for you if you are setting up a dedicated server manually.
The entire goal of the article was to allow you to still be able to change the files, with "you" in this case expected to be someone accessing a shared host over FTP. You're not expected to have root access to the server.
Robots.txt and Google
I am also negatively positioned against the robots.txt file. I don't like it at all to announce publicly the directory tree of my Joomla sites.
Considering the recent changes in Google's algorithms, that are now looking for Images, CSS and JS files, in order to fully fetch and render a webpage, I am looking for ways to allow the ...
You can find a solution here:
This will block robots.txt from everyone except googlebot, Yahoo Slurp and msnbot.
But again, Why would you want to hide it? It is perfectly OK to keep robots.txt accessible.
Pretty much every website ...
You can't, robots.txt is meant to be publicly accessible. If you want to hide content on your site you shouldn't try to do it with robots.txt, simply password protect any sensitive directories using .htaccess or similar.
I was having the same problem, and found a solution.
Disable the following items:
public $ caching = '';
public $ cache_handler = 'file'; # (replace memcache, per file)
public $ cachetime = '1600';
public $ memcached_persist = '0'; # I was in '1'
public $ live_site = ''; # (remove the full domain name)
public $ gzip = '...
You should probably look into the RokSprocket module. Make sure both Joomla and RokSprocket is up to date, and other extensions as well.
If everything is up to date, try reinstalling RokSprocket.
The RocketTheme forum might also be able to help
The Joomla .htaccess includes many rules to rewrite your urls and secure your website. You could copy them to your vhost configuration, but, frankly, I would'nt recommend it: for starters, it seems like the kind of job giving you no benefit at all. Then some rules may change when you perform an update, and then you'll have to edit your vhost config again.
As enable of Gzip compression will add <IfModule mod_deflate.c> line to your .htaccess file. SO the module should be enabled to be used by Apache.
You can ...
For website performance test you can use some online service like:
For server/application you can try with one of this posible solutions:
What is .htaccess?
.htaccess is a configuration file for use on web servers running the
Apache Web Server software. When a .htaccess file is placed in a
directory which is in turn 'loaded via the Apache Web Server', then
the .htaccess file is detected and executed by the Apache Web Server
software. These .htaccess files can be used to alter the ...
Just upload the upgrade package to the server via ftp or extract in cpanel file manager.
You will see an error after installation in the administration site only.
Go to Extensions, Manage, Database and press "FIX" Button.
The problem is likely your HTTPS redirect. You are likely redirecting to HTTPS at the beginning of your .htaccess file, and later redirecting to HTTP. Another scenario is when your Joomla website is set to use HTTPS, but there is a redirect to HTTP in the .htaccess file.
Your problems could be related to a number of reasons:
PHP version (Joomla 2.5 is not built to run on PHP 7)
Try to set your new server to PHP 5.6 This is often done through your cPanel, or ask your hosting provider.
Error during transfer (missing or corrupt files)
Try using Akeeba Backup for the transfer. Version 4.7.7 should work on Joomla 2.5.
Those 403 are on pages you are browsing, or for assets like css, js, images files etc?
403 error means, that access is forbidden for the requested file.
Since you moved your site:
Check your htaccess file for any possible required modifications, to match your site's new location.
Those 403 errors, can be on requests for external to your joomla site ...
Since the error message is generated by Joomla, it's not an Apache error.
Joomla reports that the requested view was not found. When an Url request is received, it's routed to the right component (view), and the rest of the associated modules are shown.
If there's any misconfiguration in the generated Url, you get: Joomla Error : 500 View not found [name, ...
This appeared to be an error due to JoomFish Component. My lang was switched to the translated language (without knowing) and causing Error 500 (that I could solve by re-maping better migrated data in database, eww)... If I cleared my cookies, I would get the default language and the Error 500 would be gone ...
Also, as I migrated from jUpgrade, that copies ...