Roundcube Server Error Forbidden - php

I have installed roundcube mail on my web server on rackaspace cloud sites. It worked fined till today morning it just started popping up with the Server 403 Error.
The result in the ajax call comes as Invalid Request.
The only change i made was, i changed the timezone on there server to Sydney/Australia which is by default set to America because the server is located there.
Thanks

I know I'm digging up the deads, but it could help some people getting the same problem in the future. In my case (Debien Wheezy), it was a wrong setting (I don't know which one...) on my php.ini file. When I updated PHP and my config file was replaced with the one from Debian, everything suddenly went right.

Related

500 Internal Server Error After DNS Changes

I changed my DNS to my new server on iPage. My previous server was AWS and now I got this error message:
I used to access to my site from here http://matchmakinginstitute.ipage.com/ but now is not working either.
So both links:
http://matchmakinginstitute.ipage.com/
http://matchmakinginstitute.com/
Are showing me the same error. I checked my error log file and I have only 1 line:
1479164063:
/hermes/bosnaweb03a/b2364/ipg.matchmakinginstitute/ssv3_payload_extractor-aU0H89Pshc.php
startup
Does somebody know what else can I do to fix this issue?
Thanks
Keep in mind DNS changes can take up to 48 hours to take effect.
If it's still not working after 48 hours i would suggest reverting the DNS changes and try again.
https://godaddy.com/help/what-factors-affect-dns-propagation-time-1746
Your page seems to be working fine now, did waiting do the trick ?

Apache in MAMP Pro 4 has stopped working, refuses to start

Have been using MAMP Pro for a fair while - version 3 primarily, upgraded to 4 a while ago.
I haven't had any unusual issues at all, but today the Apache service failed to start, telling me to check the error logs. The logs were blank unfortunately... I've made no system configuration changes, no changes to MAMP/MAMP Pro. Shut down my system yesterday, started today, it no longer works...
I've tried numerous suggestions found via Stack Overflow and Google without any success.
Even after completely uninstalling and re-installing MAMP Pro I am unable to get the service to start.
Nothing appears in the logs...
When starting it manually on the command line it comes up with a PHP related error:
$ Applications/MAMP/bin/apache2/bin/apachectl start
httpd: Syntax error on line 135 of /Applications/MAMP/conf/apache/httpd.conf: Cannot load /Applications/MAMP/bin/php/php5.2.17/modules/libphp5.so into server: dlopen(/Applications/MAMP/bin/php/php5.2.17/modules/libphp5.so, 10): image not found
The confusing thing is that I don't have PHP 5.2.17 specified anywhere, at all - according to MAMP Pro it should be using PHP 7.0.12.
If I add PHP 5.2.17 to MAMP using the appropriate MAMP Pro dialogs, Apache still fails to start via the MAMP Pro interface. I can now start it manually from the command line however, but none of my virtual hosts/etc seem to be loaded.
apachectl -V tells me it's using /Applications/MAMP/conf/apache/httpd.conf, but there is nothing in that file that has any reference to any of the configs generated in /Library/Application Support/appsolute/MAMP PRO/conf
It also looks like hosts entries aren't added to /etc/hosts.
Even if I tell /Applications/MAMP/conf/apache/httpd.conf to do nothing but include /Library/Application Support/appsolute/MAMP PRO/conf/httpd.conf (and manually add entries to /etc/hosts) it still doesn't seem to work at all...
I and my colleagues are at a complete loss, especially given it was working yesterday...
Has anyone had any issues like this?
I managed to fix the similar issue you had.
My Apache server was working fine and then following updating to 4.0.6 I experienced similar issues.
There were 2 things I did to fix the issue. I was getting the same error where it couldn't find a php file in 5.2.17. After fixing that by adding 5.2.17 to MAMP I experienced an apache error regarding user permissions.
(22)Invalid argument: getpwuid: couldn't determine user name from uid 4294967295, you probably need to modify the User directive
File > Edit Template > Revert ALL Templates to Default Settings.
Save & restarted the servers and all worked finally and all my hosts had retained as well.
I had previously entered a custom line in my httpd.conf file that for countless versions had copied across fine however it looks like the folder structure had changed and so couldn't locate it causing the unusual error about User permissions. I have since re-entered the custom line with the correct structure and all working fine again.
Hope this helps.

how to fix -ERR_CONTENT_DECODING_FAILED in Wamp

I have Drupal7 site. It was running fine with no issues. But suddenly I am getting
This site can’t be reached
The webpage at http://localhost:8080/mysite/ might be temporarily down or it may have moved permanently to a new web address.
ERR_CONTENT_DECODING_FAILED
Its not the issue in any specific browser, but same error with any browser.
Checked links:-
Error 330 (net::ERR_CONTENT_DECODING_FAILED):
http://stefantsov.com/fixing-err_content_decoding_failed-in-apachephp/
https://www.howtoforge.com/firefox-content-encoding-error-google-chrome-error-330-net-err_content_decoding_failed-unknown-error
I tried reinstall, reimport database etc things but same error persists.
Its been now about 24hours getting this error.
What should I do now to get rid of this error & re-run my site smoothly.
Other Info
Drupal 7
wamp 2.5
php5.5.12
Any help highly appreciated.
I was facing the same issues in xampp server on localhost.
I spend almost 2-3 hours to figure it out so i am sharing the solution to save someone else time. Below is the solution that work for me.
1) Edit the php.ini files of xampp/wampp
2) Enable the extension zlib.output_compression = On If it will be Off
3) Un-comment the code from ;zlib.output_compression = On to zlib.output_compression = On in commented using ";"
Error 330 seems to be linked to when a site's HTTP response headers claim that the content is gzip encoded, but it isn’t. Are you using gzip compression?
Try turning it on, or off via the htaccess file, or check here for other alternative ways to enable it. https://varvy.com/pagespeed/enable-compression.html

Hosting Prestashop on iPage: Front office works, but can't log into back office, there is no error

Seems like people misunderstood my intention, I didn't mention iPage
before, but since I found my solution and it is somehow related to the
hosting provider I changed the title. Should anyone get into the same
problem as I did they would be searching this on the internet and find
this post which is exactly what I did before
I just migrated my prestashop from local host to a live server (iPage). Which means to a different domain. I've tried to follow the instruction from here Moving Prestashop Documentation. First I got problem with the backoffice ui because I used to put the installation in a folder. So I need to update the folder to '/' from my local, and I also update the domain to my own domain. After that I uploaded all my files and database to the server. And the front office works well. The backoffice login page also shows up. But when I try to login it does this:
Then it just freeze, it doesn't show any error report. Nothing.
There is no problem in the console, and the http requests seem fine too.
I've also turned on the debugging mode from the defines.inc.php
define('_PS_MODE_DEV_', true);
I've increased the max_memory from php.ini to 256M
This is so frustrating, I don't know what to do anymore.
PHP Version 5.3, MySQL Version 5.5.44, and OS Ubuntu 12
EDIT:
Wait a minute, the http request return the entire login page for some reason. But there is no error message in the source. There is just this:
<script type="text/javascript">
var img_dir = '/img/';
var more_errors = 'There are some errors.';
var one_error = 'There is an error.';
</script>
I use iPage hosting and I checked the error log from the menu CGI and Scripted Language Support > Check Error Logs. It says:
PHP Warning: Unknown: POST Content-Length of 150 bytes exceeds the
limit of 120 bytes in Unknown on line 0
Then I found out that my post_max_size parameter in php.ini is messed up. It's finally fixed now. Thanks everyone...

Http request failed after site migration - server issue

So I have a website built in php and it was working perfectly on one server, I then moved the website to a server I have on Digital Ocean and am running into several errors, they seem to be based around http request failures while using the imagick library...
I was hoping to not to have to start debugging this from a code point of view as it was already working perfectly and would prefer to change server settings.
Fatal error: Uncaught exception 'ImagickException' with message 'Imagick::__construct(): HTTP request failed! HTTP/1.1 404 Not Found .
I cannot figure out what differences there, on both server allow_url_fopen is set to on.
The php version is different, 5.520 on the original server, 5.5.9 on the new server.
The versions of imagick are the same. I am also getting some other errors using the mpdf library but I will try deal with these later (Im hoping if I can resolved the first ones these ones will also get resolved).
My question is , is there possibly any other setting on the server I should be looking out for that may be causing these php errors?
EDIT:
Just to add more information, i can get rid of some of the errors by changing the file path https://www.example.com/myimage.jpg to /var/www/example/myimage.jpg . This solves some of the errors but I would rather get the root of the issue thats causing it not to work in the first place, because I feel that its the same problem thats causing other errors.
The error code says it: 404, file not found. You are probably using the wrong URL.
Are you able to fetch https://www.example.com/myimage.jpg using a webbrowser?
On several popular linux distros, /var/www/example/myimage.jpg would be served at https://www.example.com/example/myimage.jpg instead of https://www.example.com/myimage.jpg with the default configuration.
[edit]
It just came to my attention that the URL is HTTPS, there is a possibility that the script is rejecting the server certificate. Try with regular HTTP - no point in using SSL if the file is on the same machine.

Categories