• Welcome to the Chevereto User Community!

    Here, users from all over the world come together to learn, share, and collaborate on everything related to Chevereto. It's a place to exchange ideas, ask questions, and help improve the software.

    Please keep in mind:

    • This community is user-driven. Always be polite and respectful to others.
    • Support development by purchasing a Chevereto license, which also gives you priority support.
    • Go further by joining the Community Subscription for even faster response times and to help sustain this space
  • Chevereto Support CLST

    Support response

    Support checklist

    • Got a Something went wrong message? Read this guide and provide the actual error. Do not skip this.
    • Confirm that the server meets the System Requirements
    • Check for any available Hotfix - your issue could be already reported/fixed
    • Read documentation - It will be required to Debug and understand Errors for a faster support response

CloudFlare wrong IP Log

Status
Not open for further replies.
D

DDexter

Chevereto Member
Hey!

IP Logs dosen't work with cloudflare. It's show cloudflare ip not user ip
 
Last edited:
Dashboard >Settings >External services > Enable CloudFlare
 
Most likely CloudFlare (again) changed the header that indicates that thing. I have enabled CloudFlare in the demo website, will try to see what is going on.
 
I'm getting real IPs on the demo so I can't replicate your issue. To be able to help you I need all details, like:

- Website URL
- Admin access (Chevereto)
- FTP access

Send those to inbox@chevereto.com
 
I can confirm that the bug is real. I've patched your website already.
 
Who are affected by this bug? I am asking because I just tested it by uploading on my website and it logged my IP address. It is limited to guest users or non-admin?
 
Is hard to tell who is affected by this, I found very odd $_SERVER entries on that website so I ended up making a general patch for it. Most likely this website has custom headers or things like that.
 
I can confirm that this bug has been already fixed for the upcoming release (v3.8.4).
 
Status
Not open for further replies.
Back
Top