Advanced search  

News:

cpg1.5.48 Security release - upgrade mandatory!
The Coppermine development team is releasing a security update for Coppermine in order to counter a recently discovered vulnerability. It is important that all users who run version cpg1.5.46 or older update to this latest version as soon as possible.
[more]

Pages: [1]   Go Down

Author Topic: cpg1.4.5 install sending wrong username to mysql ?  (Read 2745 times)

0 Members and 1 Guest are viewing this topic.

josswern

  • Coppermine newbie
  • Offline Offline
  • Posts: 2
cpg1.4.5 install sending wrong username to mysql ?
« on: April 24, 2006, 09:13:02 am »

well, I saw many similar probs mentioned here, but none of them seems to directly apply here:
I'm trying to install cpg1.4.5 and get this:
Code: [Select]
Could not create a mySQL connection, please check the SQL values entered

MySQL error was : Access denied for user: 'josswern@myhost.myisp.de' (Using password: YES)
- problem seems to be that 'josswern@myhost.myisp.de' is beeing sent to the mysql host (which is _not_ localhost in my case) instead of just 'josswern', which I filled in the form (and which is approved to work together with specified password).
so, is there any way to tell cpg to just send the plain username as typed, instead of automatically appending the hostname ?
« Last Edit: April 24, 2006, 10:22:34 am by Nibbler »
Logged

Nibbler

  • Guest
Re: cpg1.4.5 install sending wrong username to mysql ?
« Reply #1 on: April 24, 2006, 09:41:54 am »

Coppermine doesn't append the hostname - that's just the way MySQL displays the error message. It displays the host name you are attempting to connect from.
Logged

josswern

  • Coppermine newbie
  • Offline Offline
  • Posts: 2
Re: cpg1.4.5 install sending wrong username to mysql ? [solved]
« Reply #2 on: April 24, 2006, 10:18:24 am »

ok, thanks - I just realized I had used a wrong username (the one I use on my local testserver), corrected that and all is ok.
sorry for the noise  :'(
Logged
Pages: [1]   Go Up
 

Page created in 0.015 seconds with 15 queries.