Problem: CSS was being applied to the site but after switching to reverse proxy and adding a security cert while changing nothing else, the CSS no longer loads.
Details: Initially the website was using keter only with no security cert or reverse proxy. The site worked fine as intended. The yesod-devel command correctly renders the site. Once compiled, the styling does not appear on the final site. Before the switch to reverse proxy, everything worked as desired. No other changes were made except to config files related to the reverse proxy and security cert.
Dependencies: The dependencies are at this https://gist.github.com/xave/9cdf396c1918c129aff927ab8999d456.
Workflow: The main dev machine is macOS. The server is Ubuntu. The workflow is to develop and preview on macOS, then to compile and deploy on Ubuntu.
Thoughts:All the CSS is on the page upon inspection. It just isn’t applying. This is true for multiple browsers and even for people who had never before visited the site (so not a caching issue).
Any help would be appreciated and please let me know if you need additional information.
Related
I have gitlab running behind a nginx reverse proxy on a relative url (my.domain.com/gitlab/) in a docker container. I've migrated some of my projects from Github and everything seemed fine. However when I tried to see details for an existing issue, which was migrated with the project, the website didn't load. It looked like the reverse proxy was routing back to <server-ip-address>:<port> again, instead of the url. I also tested what happens when I create a new issue, because I thought maybe the migration didn't work, but it had the same effects. After a bit more testing I figured that typing in the issue-number in the url works though e.g. my.domain.com/gitlab/group-name/project-name/-/issues/4.
I'm really confused now, whether this is a problem with nginx or gitlab itself. Did anyone have similar issues?
Gitlab-Version: gitlab/gitlab-ce:14.10.0-ce.0
Nginx: nginx:1.21.6-alpine
I just downgraded Gitlab to version gitlab/gitlab-ce:14.9.4-ce.0 and it works. So I guess this is a problem with the other version and has absolutely nothing to do with docker or nginx.
Just wondering if anyone can help me on an issue I’ve been having with Browsersync issues with the Sage theme for Wordpress.
In terms of my environment, I’m using Laravel Valet, which is parked in a projects directory on my machine. The site in question is in this projects direct on a .test domain and has a self signed SSL cert from Valet.
Running yarn build successfully builds the site, however when running yarn start, the files build and successfully build every time I change a JS/SCSS file with Browsersync showing DONE Compiled in 284ms... however Browsersync is failing to proxy the valet URL, as when I go to https://localhost:3000, Chrome loads for an extremely long time and then throws ERR_TIMED_OUT. Tried in other browsers and get the same issue.
There is no firewall blocking that port, as tried with another app which works successfully
Tried with and without self signed cert from Valet, and tried http and https links from Browsersync
Tried deleting node_modules and running npm install
Tried changing the URL of the site
Tried a different proxyUrl in config.json
devUrl is definitely correct
publicPath is definitely correct as it’s building the files
Browsersync doesn’t throw any errors
Someone on the Sage Discourse recommended downgrading browsersync too but that didn't work 😞
Been looking at this for two days now and just hopelessly Googling… so just seeing if anyone has had this issue before?
Cheers!
I am developing a website using Roots.io stack (Trellis + Bedrock + Sage).
I am working, locally, on several sites and they're all working fine. Until today I reboot my computer > execute vagrant up > attempt to access the local development URL https://mysite.dev > but suddenly get an error, in Chrome, stating "NET::ERR_CERT_AUTHORITY_INVALID".
Normally, I do get a similar error, but I have the option to dismiss it. But now I do not.
Via BrowserSync, I can access the site via localhost:3000 but not using the development URL.
If you're familiar with Roots, you know that Trellis generates the SSL locally as self-signed in an automated process. So I know very little about how it works outside of their documentation.
I understand that this issue seems to be a mix-match with the SSL certificates locally, but I don't really know how to troubleshoot that. I'm thinking there is a file locally that needs to be deleted and replaced. But I don't know how to generate a replacement if that's the case.
I have spent about an hour reading any articles I could find on the topic but none seem to really explain precisely what's going on in a way I can apply.
Update: Ultimately I'm looking for a way to add an exception for the ticket in Chrome. I was able to do it in Firefox and it's working there.
Thank you.
Short Answer: Don't use .dev extensions in your local URLs as this is now a real domain name extension no longer reserved for localhost.
Long Answer: https://ma.ttias.be/chrome-force-dev-domains-https-via-preloaded-hsts/
You can either
Import this certificate using Chrome's Options > Manage Certificates > Import
Or simply ignore SSL errors launching chrome with args --ignore-certificate-errors like /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --ignore-certificate-errors &> /dev/null & (not recommended).
I'm having trouble getting my Posboxes to work with my remote Odoo v10 server with Nginx and SSL.
I have tried configuring Nginx to send request to /pos/ over http. This results in a Mixed Content error in Safari and Chrome.
As I am using iPads, I cannot make Safari ignore this. This is also the result when I try to serve the /pos/ directory over https.
This results in the browser not being able to connect to the Posbox.
I've read and tried the solutions in these GitHub issues, with no success:
https://github.com/odoo/odoo/issues/2031
https://github.com/odoo/odoo/issues/3156
Does anyone have a working Nginx config example for use with Odoo 10?
if you are still facing this issue, then here is the fix. Please go through this blog:
https://webkul.com/blog/serve-odoo-posbox-over-https
I have also upgraded the ODOO POSBOX base image so that it will have nginx pre-installed in it, which can be easily connects with ODOO served over https.
Download Link : https://drive.google.com/file/d/0B1dx-UuV9AOYbWZSNG1GVjBPOTQ
I hope it will work.
I've been using codekit for ages now, and now I've been using the version 3 since it came out.
I really like this app, but there's something I never really understood and I decided to post it here (hoping to finally understand how this works and how to make it works like I want).
I have MAMP pro installed, with some hosts.
Let's say I have this list of hosts with (fake) document root:
localhost -> documents/site1/dist
test -> documents/sitetest/dist
and let's assume that test is a wordpress site having the site url set to
http://test/ in the database.
In codekit, when I enable the browser refresh, the bottom options asks me to write down the address I would visit to see my website.
Now, if I navigate to http://test/ my WordPress website loads and I am able to see everything.
In codekit I then setup the browser refreshing options to be the following:
Animation: ticked
Refresh Delay: 0.0 seconds (default)
Preview: empty
Document-Root Subpath: empty
External Server Required: on
External Server Address: http://test/
Then when I click on the green dot (server) to preview my website, I'm expecting codekit to navigate to http://test:5757 and to properly display my website. This, unfortunately, is not the case. When I click on the preview (or server, it doesn't really make any difference for me) codekit navigates to my mac IP and the website is either not loading or loading without any external resource.
I don't think the issue is in the way I load the resource in WordPress (i use enqueue sources properly, and the website without using codekit refresh function works, load and displays as meant to).
So far, I always switched my current project to use the localhost host (changing the document root in MAMP pro) and then telling codekit to use the localhost ip as external server, but now it's a bit more complex, as I have way more projects and I was hoping not to change back and forth the document root to use codekit built in refreshing feature.
Is it possible? am I missing something here?
I read all I was able to find as well as watched the videos on codekit, but this bit here is still a bit unknown to me and any help would be really appreciated.
Thanks
PS: No need to mention I am on a MAC, right? :)
I don't believe I actually managed to fix this.
I'll leave the answer here in case somebody else is facing the same issue.
The problem I had was that my website http://test/ was using a theme called test.
Codekit, for refreshing the browser, uses a simple string search and replace in the URL, and so everything that looked like "test" in the url was replaced by the internal ip.
Quick example:
http://test/wp-content/themes/test/index.php
became
http://192.168.0.1:5757/wp-content/themes/192.168.0.1:5757/index.php
and of course no file where loaded successfully, as the path was wrong.
To fix this?
Just change the MAMP pro address to something that won't be present in the URL (in my case, the MAMP pro host called test became dev.test and problem solved.