I think I might have touched something wrong in my server configuration (tinkered with a LOT of things to get some weird software running) and now phpMyAdmin is acting up.
First it gave me that "Error 330 (net::ERR_CONTENT_DECODING_FAILED): Unknown error." (chrome specific), then I set zlib.output_compression = Off in php.ini (rebooted apache) and how the css file is not working.
I know phpmyadmin is just the symptom here, if anyone has a clue about what is going on, I'd be eternally grateful.
If you need any configuration file simply ask and I'll post/pastebin it (I'm on a FreeBSD server btw.)
Turns out mod_suphp was creating conflicts preventing any setting of Content-types via header(); I deactivated it in httpd.conf and now everything works perfectly.
Related
Don't know, maybe someone had the same problem before..
I've got a correctly configured ssl certificate in my server.
If I activate prestashop ssl mode, then several pages generate an infinite redirection loop warning....
I really can't figure out why..
One thing I can say, is that in backoffice, clicking on the ssl acivation link, it does not activate it: it stays, silently, no rerrors, nothing.
So to activate ssl I had to manually change the relevant config variable on the DB.
This could maybe be a symptom of something wrong on the server?
Anyone had the same problem?
Thank you
Apart from upgrading to v1.6.0.11, the solution was to add SetEnv HTTPS On at the very top of .htaccess. That's because several prestashop functions rely on $_SERVER['HTTPS'] and/or $_SERVER['SSL'] vars to guess the urls. One of the most notable functions using them and itself used by many others is Tools::usingSecureMode(). Simply those vars weren't visible before adding SetEnv HTTPS On.
Anyway, this is not to be considered a universal solution, because for example in my local MAMP installation I didn't have the same issue: just worked. I only needed the tweak for the remote server.
Beside this, also note that in backoffice, unde url/seo prefs, I disabled the apache multiviews.
Hope it helps
Sometimes, for no real reason I get the following console message and a completely blank screen after deploying code to the server:
net::ERR_INCOMPLETE_CHUNKED_ENCODING
An Apache restart fixes it but I can't see why it happens. The file system changes but not any config. I've never encountered it when not doing a deployment, so something about the file system changing whilst apache is running seems to cause it.
The document root is a symlink (current/) to the latest release folder.
This might not be your problem, but it solved it for me so i'm going to throw it out there anyway - setting opcache.fast_shutdown=0 fixed it. It is disabled by default according to the php docs
but had been enabled in our setup.
I had this problem with phpmyadmin. Try disabling your antivirus.
Sorry for the imprecise wording of this question however I have really hit a wall here.
I have installed XAMPP/LAMPP on a machine running Debian. I then installed joomla on the installation of LAMPP. Everything is running correctly. I am now trying to add either a symlink or an Alias to the httpd.conf file. Which httpd.conf file should I edit?
I think I have somewhat correctly added something to the relevant files becuase the access log returns this:
GET /Archived/test.html HTTP/1.1" 403 1043
Obviously i'm getting 403 errors when I try to connect to the directory. I have tried applying permissions to everywhere I could think of. Any suggestions would be extremely helpful, thanks!
A client has a website running on a dedicated host (either developed, nor managed by myself) in which Apache is generating a very strange behavior.
When the requested url is of the type:
http://obituarieshelp.org/aboutus.html/whatever_here
it actually loads 'aboutus.html' if it exists, even though 'whatever_here' does not exist, and 'aboutus.html' is not a directory.
I took a look at the htaccess file, and everything seems to be fine. I am sure it is apache misconfigured somehow, but for the love of me, I cannot seem to find anything that could point to the problem in httpd.conf
Has anyone experienced the same, or has any suggestions as to why this would be?
This is controlled by the AcceptPathInfo HTTPd directive. The remainder of the path after the file is made available in the PATH_INFO environment/server variable, and scripts can use it to discern additional information about the request.
I updated my MAMP to version 2 and ran into a couple of problems. I've always had my projects in a folder /Desktop/Projects and pointed my localhost there. No problem whatsoever, I could see my filelistings etc.
However, after updating, I now get a '403 Forbidden' error, stating that I do not have permission to access '/' on this server.
I'm not sure what I did before to make this work, and I suspect this has something to do with Apache's and/or MAMP's settings? Could someone perhaps give me some pointers? Thanks.
PS: Not sure if this is the right Stackexchange site, but Webmasters didn't have a MAMP tag, so I figured I'd post it here. Thanks a lot.
Guessing you didn't set the Disk Location correctly...
In MAMP, click the HOSTS tab, there you'll see Disk Location.
You can choose the directory here, and click Permissions to make sure things are set correctly.
The path to your web-root should be something like /Users/cabaret/Desktop/Projects