Search found 7 matches
- 11 Nov 2014, 11:42
- Forum: Help
- Topic: ERROR: invalid byte sequence for encoding "UTF8"
- Replies: 8
- Views: 6638
Re: ERROR: invalid byte sequence for encoding "UTF8"
Hello The problem was that I have a queue called "Fila de Serviços" and the "ç" character was given the error, I changed it to "c" and it solved. But this does not resolve the issue that PostgreSQL is not accepting "especial" characters like "ç" and ...
- 23 Oct 2014, 12:05
- Forum: Help
- Topic: ERROR: invalid byte sequence for encoding "UTF8"
- Replies: 8
- Views: 6638
Re: ERROR: invalid byte sequence for encoding "UTF8"
I will check it up and return later, Thanksjojo wrote:might be an issue with a special character which can not be used in the database (I heard of a mysql bug for the same)
- 23 Oct 2014, 11:31
- Forum: Help
- Topic: ERROR: invalid byte sequence for encoding "UTF8"
- Replies: 8
- Views: 6638
Re: ERROR: invalid byte sequence for encoding "UTF8"
OTRS 3.3.8 - Postgres 9.1jojo wrote:OTRS version, database?
- 22 Oct 2014, 20:43
- Forum: Help
- Topic: ERROR: invalid byte sequence for encoding "UTF8"
- Replies: 8
- Views: 6638
ERROR: invalid byte sequence for encoding "UTF8"
Hello This error appears when the client creates a new ticket in the screen after pressing Send The ticket is created in otrs but all blank and the client does not receive mail confirmation When debug is enabled (Frontend::DebugMode) this error does not happens, the ticket is created normally! The l...
- 15 Jul 2014, 19:18
- Forum: General
- Topic: LDAP OTRS TLS
- Replies: 5
- Views: 5047
Re: LDAP OTRS TLS
Kernel/System/Auth/LDAP.pm # ldap connect and bind (maybe with SearchUserDN and SearchUserPw) my $LDAP = Net::LDAP->new( $Self->{Host}, %{ $Self->{Params} } ); if ( !$LDAP ) { if ( $Self->{Die} ) { die "Can't connect to $Self->{Host}: $@"; } else { $Self->{LogObject}->Log( Priority => 'er...
- 15 Jul 2014, 16:02
- Forum: General
- Topic: LDAP OTRS TLS
- Replies: 5
- Views: 5047
Re: LDAP OTRS TLS
ldaps would be ssl ldap. A search might help For instance, 389 is known to not be ssl but 636 is Our LDAP uses TLS on port 389. It is an OpenLDAP server. For example, our Linux machines are using the following to search an authenticate on LDAP: uri ldap://srv-ldap-consumer-01.edu.br ssl start_tls U...
- 15 Jul 2014, 15:41
- Forum: General
- Topic: LDAP OTRS TLS
- Replies: 5
- Views: 5047
LDAP OTRS TLS
Hi everyone Does someone knows how to make LDAP work with tls in OTRS? My configuration is: ... $Self->{'AuthModule::LDAP::Host'} = 'srv-ldap-consumer-01.edu.br'; ... $Self->{'AuthModule::LDAP::Params'} = { verify => 'optional', cafile => '/etc/ssl/certs/cacert.pem', sslversion => 'tlsv1', port => 3...