Typo3 V9 behind Reverse Proxy Apache2 - Backend not working - typo3

just updated Typo3 V9 (already running nicely behind reverse proxy) to the latest patchlevel on a test server without reverse proxy.
After migrating back everything is working fine, but I can't login to the backend. It redirects me to the internal webserver domain e.g. local.app1:8099/typo3.
I have everything set up, standard for reverse proxy. What can it be?
LocalConfig:
'reverseProxyHeaderMultiValue' => 'first',
'reverseProxyIP' => '12.345.678.90',
'reverseProxyPrefixSSL' => '',
'reverseProxySSL' => '*',
'sitename' => 'Foo',
'systemLogLevel' => 2,
'systemMaintainers' => [
1,
],
Best
RK

Solution:
Strange it didn't came up elswere. We Finally found a working fix here (at least for our config):
https://forge.typo3.org/issues/91414

Related

Sudden Axios Error not properly sending parameters

April 26 2022 The system that we are working is suddenly not working, I found out that the request data from frontend to backend suddenly became weird.
The regular request
array ( 'email' => 'xxxxx+1#gmail.com', 'password' => 12341234, )
When running Axios:
When I tried to use Ajax, the request is the normal one. However we are using axios for the majority of the project. Is someone else having the same error?
using the script: https://unpkg.com/axios/dist/axios.min.js

TYPO3 v9 using Microsoft SQL Server 2016

PHP 7.3
pdo_sqlserver_73_nts (installed)
sqlserver_73_nts (installed)
I'm trying to connect a new install of TYPO3 (v9.5.7) to an instance of SQL Server 2016 running on the same box.
I'm able to establish a connection to the database, using the example from php.net: https://www.php.net/manual/en/function.sqlsrv-connect.php so I'm confident the server is accessible.
A similar question has been asked for v8 here Install TYPO3 8.7.7 with SQL Server on IIS and it's recommend that you ammend the DB settings in LocalConfiguration when the installer is at stage 2 and essentially "trick" the installer to connect to SQL Server.
I've done that and for some reason it won't connect,
'DB' => [
'Connections' => [
'Default' => [
'charset' => 'utf-8',
'dbname' => 'typo3_db',
'driver' => 'sqlsrv',
'host' => 'localhost',
'password' => 'password',
'port' => 1433,
'user' => 'username',
],
],
],
Is there anything wrong with this connection string? I can't seem to find any other working example.
Thanks as always,
i had the same problem.
Try to set the full name of your mssql server:
'host' => 'COMPUTERNAME/DBNAME',

Perl Webservice SSL Negotiation Failure

I am trying to call a web service using ssl. It gives following error:
500 SSL negotiation failed:
I searched forums and applied offered methods but none of them worked.
2 methods I applied are listed below:
1-) setting enviroment before call:
$ENV{PERL_LWP_SSL_VERIFY_HOSTNAME} = 0;
2-) passing parameter ssl_opts => [ SSL_verify_mode => 0 ] to proxy:
my $soap = SOAP::Lite
-> on_action( .... )
-> uri($uri)
-> proxy($proxy, ssl_opts => [ SSL_verify_mode => 0 ])
-> ns("http://schemas.xmlsoap.org/soap/envelope/","soapenv")
-> ns("http://tempuri.org/","tem");
$soap->serializer()->encodingStyle(undef);
Is there any solution for this?
... Connection reset by peer at /usr/lib/perl5/vendor_perl/5.8.5/i386-linux-thread-multi/Net‌​/SSL.pm line 145
You are running a very old version of Perl (from 2004) together with an old version of the SSL libraries (i.e. Crypt::SSLeay instead of IO::Socket::SSL) and my guess is that this goes together with using a very old version of the OpenSSL libraries for TLS support. This combination means that there is no support for SNI, no support for TLS 1.2 and no support for ECDHE ciphers. Many modern servers need at least one of these things supported. But connection reset by peer could also mean that some firewall is blocking connections or that there is no server listening on the endpoint you've specified. Or it could mean that the server is expecting you to authorize with a client certificate. Hard to tell but with a packet capture of the connection one might provide more information. And, if the URL is publicly accessible publishing it would help too in debugging the problem.

TYPO3 6.2 - 404 error page with realurl

I've a TYPO3 CMS 6.2.15 running with realurl and the following LocalConfiguration.php:
'FE' => array(
'pageNotFound_handling' => '/404/',
'pageNotFound_handling_statheader' => "HTTP/1.0 404 Not Found",
...
), ...
I've created a page called "404" and tested if I can call that page like page.ending/404/. It works. But now I try a non-existing page like page.ending/asdfasdf/ and get the default Apache Unauthorized page. Why is that?
At least I get the correct 404 header information but why does it not redirect to the 404 page?
You have to change the corresponding line to:
'pageNotFound_handling' => 'REDIRECT:<your-404-url>',
First check php function curl is enable or not in your php.ini file. if curl is disable then first enable this function.
Then use below code in your LocalConfiguration.php file.
'FE' => [
'pageNotFound_handling' => '/your-page-name/',
],

Cake Email Times Out During Send

I'm trying to use CakeEmail in a web application, but I keep running into a timeout error. All my Googling and Stacking only give me the idea that something is not configured correctly, but I can't seem to find what config option I'm missing or filling incorrectly. I'm trying to send using my Gmail account.
Gmail Config:
public $gmail = array(
'host' => 'ssl://66.249.93.111',
'port' => 465,
'timeout' => 30,
'username' => 'my_gmail_account_name',
'password' => 'my_gmail_account_password',
'transport' => 'Smtp'
);
in app/Config/email.php
Email code:
$Email = new CakeEmail('gmail');
$Email->from(array('my_gmail_account_name' => 'Dev'));
$Email->to('my_gmail_account_name');
$Email->subject('Export Email Test');
$Email->send('This is a test email for ExportJobs.');
(As an additional note, the code that runs here is as part of a Cake Console program, so these methods are called when I run Console/cake file_name from the command line; also, that IP is the Gmail SMTP IP. When I try using the name, I get some DNS issue).
Does anyone happen to see what I'm missing?
Thanks for your time!
I found the problem I was having; it's a pretty silly error.
I completely forgot that to use the gmail domain for SMTP, I have to preface the domain name as "smtp.gmail.com". Once I did that it used SMTP and worked just fine.