Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

This page contains a script from unauthenticated sources #482

Closed
sebu77 opened this issue Feb 21, 2014 · 12 comments
Closed

This page contains a script from unauthenticated sources #482

sebu77 opened this issue Feb 21, 2014 · 12 comments
Labels

Comments

@sebu77
Copy link

sebu77 commented Feb 21, 2014

Hi,
I'm running wallabag 1.5.0 on my server and my web browser is always displaying a shield with "This page contains a script from unauthenticated sources".
It breaks the page structure.
Thanks.

@tcitworld
Copy link
Member

Hi,
Which browser are you using ?

@sebu77
Copy link
Author

sebu77 commented Feb 21, 2014

It's the same result with firefox and chrome.

@tcitworld
Copy link
Member

With firefox, go into Tools > Page Info > Media and see which file is starting with http instead of https.
If you find none, it should be the Google fonts used in some themes. This has been fixed in #464

@tcitworld
Copy link
Member

Also, it may be fixed in latest version 1.5.2. Give it a try. :) http://www.wallabag.org/downloads/

@sebu77
Copy link
Author

sebu77 commented Feb 21, 2014

themes/baggy/img/favicon.ico
themes/baggy/img/apple-touch-icon-144x144-precomposed.png
themes/baggy/img/apple-touch-icon-72x72-precomposed.png
themes/baggy/img/apple-touch-icon-precomposed.png
themes/baggy/img/logo-w.png

@sebu77
Copy link
Author

sebu77 commented Feb 21, 2014

No changes with version 1.5.2
Thanks

@tcitworld
Copy link
Member

That's strange. I guess your web server doesn't want to serve .png files as https, because it should detect whether the files are available in secure mode or not.
Which webserver are you using ? Can you post your vhost configuration ?

@tcitworld tcitworld added the Bug label Feb 21, 2014
@sebu77
Copy link
Author

sebu77 commented Feb 21, 2014

I'm using apache and nginx.

Here my vhost:
<VirtualHost *:8080>
ServerAdmin webmaster@localhost
ServerName wallabag.xxx.com
DocumentRoot /home/seb/wallabag
<Directory /home/seb/wallabag>
Options -Indexes FollowSymLinks MultiViews
AllowOverride All
Order allow,deny
allow from all

and nginx:
server {
listen 80;
server_name wallabag.xxx.com;
rewrite ^(.*) https://wallabag.xxx.com$1 permanent;
}

server {
listen 443 ssl;
server_name wallabag.xxx.com;
client_max_body_size 100M;

    ssl_certificate /root/server.crt;
    ssl_certificate_key /root/server.key.uncrypt;

    access_log  /var/log/nginx/wallabag.access.log;
    error_log  /var/log/nginx/wallabag.error.log;

    location / {
            proxy_pass http://apache;
            proxy_set_header    Host $host;
            proxy_set_header Accept-Encoding "";
            proxy_set_header X-Real-IP $remote_addr;
            proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    }

}

@tcitworld
Copy link
Member

I guess using nginx as a proxy is the source of problems. You should add a ssl configuration to Apache too, because it's apache which is asked to serve these files. Take a look at this if needed, but you seem to know how it works. ;)

If it doesn't works, an you try to access directly to [yourhttpsbaseurl]/themes/baggy/img/apple-touch-icon-144x144-precomposed.png and see what outputs tail /var/log/nginx/wallabag.access.log and same with error_log.

@sebu77
Copy link
Author

sebu77 commented Feb 21, 2014

Theses images are not present with this names in the archive.
Here's the content of the wallabag/themes/baggy/img folder:
apple-touch-icon-114.png
apple-touch-icon-120.png
apple-touch-icon-144.png
apple-touch-icon-152.png
apple-touch-icon-57.png
apple-touch-icon-72.png
apple-touch-icon-76.png
apple-touch-icon.png
bg-select.png
favicon.ico
logo.png
logo.svg
logo-wallabag.svg
apple-touch-icon-152.png
logo-w.png

@tcitworld
Copy link
Member

Well, there is problems with the Apple icons names, but the favicon and the logo should be properly served, so there is something else.
Have you tried what I said ?

@sebu77
Copy link
Author

sebu77 commented Feb 21, 2014

Yes, configuring apache with SSL solves this issue.
Thanks.

@sebu77 sebu77 closed this as completed Feb 21, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants