I set up an xwiki instance on my internal dev server to build a new documentation site for our company. Everything went great and after everything was signed off on, we moved the site to a LiquidWeb server instance.
I set up a new xwiki server and imported the content from the dev server.
Now, every time I create a new page, or edit and existing page, I get this at the bottom, and it never goes away, unless I click on it.
Any ideas for fixing this?
Something that your developer console says? You can open it in chromium browsers with F12.
Yes, looks like there’s a ton of http to https errors:
[Error] Cannot load http://help.checkinpos.com/wiki/internaldocs/jsx/CKEditor/EditSheet?sourceMap=true&minify=false&v=17.1.0&xwiki-version=17.1.0&fast-diff-version=&bs3typeahead-version=4.0.2 due to access control checks.
[Warning] [blocked] The page at https://help.checkinpos.com/wiki/internaldocs/view/Online%20info%20for%20Checkin/ requested insecure content from http://help.checkinpos.com/wiki/internaldocs/jsx/CKEditor/Translations?sourceMap=true&minify=false&language=en. This content was blocked and must be served over HTTPS.
I’ve been searching for ways to fix the errors, but none of the remedies, such as:
I can’t find the xwiki config file, and the Tomcat config file doesn’t have the section shown in this topic.
Could definitely use some help.
I found the xwiki.cfg file @ /usr/local/tomcat/webapps/ROOT/WEB-INF, and added the option to force https there, no change.
I am running the site behind NPM and using it’s built in ability to request and serve SSL certs, so I guess the problem lies there somewhere?
I just don’t know how to fix it.
Finally deciphered what I think I’m supposed to add. In tomcat’s server.xml file I updated the mentioned sections to look like so:
<Connector port="8080" protocol="HTTP/1.1"
connectionTimeout="20000"
redirectPort="8443"
maxParameterCount="1000"
secure="true"
scheme="https"
/>
<Valve className="org.apache.catalina.valves.AccessLogValve" directory="logs"
prefix="localhost_access_log" suffix=".txt"
pattern="%h %l %u %t "%r" %s %b"
remoteIpHeader="x-forwarded-for"
protocolHeader="x-forwarded-proto" />
Then I added these lines to NPM’s Advanced settings:
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
But I still get:
After restarting the container.
This is driving me crazy.
None of the topics here have a clear and concise answer.
I’m still struggling with this.
Does anyone have a good set of steps that will stop the mixed content errors?
Here’s as much info as I can give. I could really use some help getting this issue resolved.
Using Docker containers to deploy xwiki and mysql with these commands:
docker run --net=xwiki-nw --name mysql-xwiki -v /opt/xwiki/mysql:/var/lib/mysql -v /opt/xwiki/mysql-init:/docker-entrypoint-initdb.d -e MYSQL_ROOT_PASSWORD=password -e MYSQL_USER=xwiki -e MYSQL_PASSWORD=password -e MYSQL_DATABASE=xwiki -d mysql:9.1 --character-set-server=utf8mb4 --collation-server=utf8mb4_bin --explicit-defaults-for-timestamp=1
docker run --net=xwiki-nw --name xwiki -p 8080:8080 -v /opt/xwiki/:/usr/local/xwiki -e DB_USER=xwiki -e DB_PASSWORD=password -e DB_DATABASE=xwiki -e DB_HOST=mysql-xwiki -d xwiki:17.1.0-mysql-tomcat
Using an external docker network to connect them.
I’m using NPM in another container to normalize the port and put an SSL certificate in play.
DNS is provided by Cloudflare
<Leia>Help me Obi Wan... you're my only hope</Leia>