Viewing 3 replies - 1 through 3 (of 3 total)
  • Hi Cedricmi,
    Actually, there are different methods of handling both connections (http & https) without having two .conf files, like this one for example.

    But anyway, as long as you have two .conf files, then yes you will need to append Wordfence falcon rules for your both .conf files.

    However, there is an easy way mentioned here -I didn’t try it in practical though!- which is worth trying.

    The only thing I will modify on the above method, is having only these lines starting with:
    # WORDFENCE FALCON ENGINE CODE
    to:
    # END Wordfence Rules

    in a separate file, let’s say /etc/nginx/wf.conf

    Then just include this file inside your server block, like that:

    server {
                    # Include Wordfence config.
    		include /etc/nginx/wf.conf;
    }

    Let me know if you have any further question,
    Thanks.

    Thread Starter Cedricmi

    (@cedricmi)

    Hi,

    Thanks for the answer.

    I tried something like that but only for the http.conf file, since there were a few lines in the wordfence rules concerning https.

    I’ll try again.

    What is strange is that although the cache told me it was populating, I could never get a page with wordfence debug info (as selected in options), with either http or https.

    I think you need to try opening your web page in Chrome incognito mode (press CTRL+SHIFT+N while using Chrome) and refresh your page there several times, then right click and choose “View page source” or press CTRL+U, scroll down the page and you should find this message at the end of your page.

    Let me know how it goes,
    Thanks.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Wordfence on Nginx with 2 conf’ is closed to new replies.