We are facing problem on highcharts when running on https. It not getting rendered. But it is fine when running on HTTP.
Its not duplicate because here all the urls follows https
Https Version
Http version
Any thoughts, please.
Related
I am creating an application using Vue.js with Vite for client-side and express.js for the server-side on docker. The server side sends the cookie as a response to Axios request front client, and I can see Set-cookie in the response-header. However, this cookie is not set to the browser. I opened the Application tab and checked the cookie, but nothing was there.
Client URL: http://localhost:3000/
Server URL: http://localhost:15173/
Both of the are running on separate Docker containers.
Environment is
Front: vue3 with vite
Sererside: nodejs with express.js
connection: Using axios
Probably, this is caused by CORS, but I don't know how to deal with that. I'm tring to solve this question fixing proxy, but so far no luck.
if anyone can help me out, that would be great. Thank you!
I tried vite.config proxy setting, but it didn't solve the situation.
I am working on a web app on http://pagesage.page and have deployed with Digital Ocean on a Docker container with gunicorn and meinheld with A and AAAA name records set up. Additionally, the appropriate ports for http have been set up for listening and responding.
Unfortunately, while the page responds to curl, ping, and ping6 requests, the page only ever loads on the Safari browser (and some IE distributions) and I can't seem to figure out why (I get DNS timeout errors whenever I try to load the page in Chrome or Firefox).
I've tried accessing the page from different machines (brand new and old), reset the DNS settings a few times, and reset the browser's cache, all with no success.
Does anyone have ideas or suggestions, or has anyone else encountered this same problem?
You have a problem with your SSL/TLS terminaison. The website is available on HTTP but unavailable on HTTPS. Chrome and FF redirect the user to the HTTPS version. It looks like the port 443 (used for HTTPS) is closed.
I have an ssl certificate(Geotrust) installed to IIS 8, listening on port 443 and running on windows server 2012-r2. This works when I access https://myapp.example.com and it shows me the standard IIS page. My problem is that I am trying to connect to the parse-server(nodejs, express) running on serverUrl: http://localhost:1337/parse. So when trying to connect to https://myapp.example.com:1337/parse
chrome says: "myapp.example.com finished the connection unexpectedly" and I cant reach the expected site.
ios-simulator says: kCFStreamErrorDomainSSL, -9806.
The connections to http works as expected on the urls described above.
I have tried to set the SSL port to 1337(and portforward 443->1337 on my router), but then I can not start the parse-server on the same port.
First time doing this, so really gratefull if anyone can point me in the right direction!
Solved by doing an reverse proxy in IIS 8.
I needed two applications in IIS and downloaded them like this: yourSite->right-click middle pane->"install application from gallery" and search & download these:
Download URL Rewrite (i downloaded 3.0)
Application Request Routing
This helped a lot:
http://weblogs.asp.net/owscott/creating-a-reverse-proxy-with-url-rewrite-for-iis
I have setup a proxy in the build file which was working perfectly on
my mac at work. But on my Ubuntu 11.04 laptop at home the proxy seems
to never return a valid response (checking with SC.ok(response)).
I have checked by curling the url:
curl -G http://localhost:4020/api/client
Output:
[{"id":"1","title":"Test","status":"1","created":"2011-07-03 07:36:44","updated":"2011-07-03 07:36:44","brands":null},
{"id":"2","title":"Arla","status":"1","created":"2011-07-03 07:43:53","updated":"2011-07-03 07:43:53","brands":null}]
Anyone got any ideas?
Thanks
Mark
I have opened an issue similar to this one. It seems that the Thin web server can't handle gzipped content from an upstream server.
If you can disable gzip on the remote server and please upvote the issue on github so that it has better chances of getting fixed.
If You are using Apache at home check Your log files (while running the app):
tail -20f /var/log/apache2/error.log
You might get this error:
Client sent malformed Host header
This is because the Host header (more precise the port) is different than Apaches standard localhost:80.
I'm setting up IIS 10 on Windows Server 2019. After I installed Let's Encrypt cert via win acme some url fails.
I've setup ApploccationPoolIdentity method for my web site. Here is my setup
So far I have most of paths are working. Fails:
account/login and account/logoff
some fonts (.woff2, woff, .ttf) see image below
All above fails with 403 Status code. But they working fine if
open localhost on my VPS
unbind hhtps (:443, ssl) and reach them using http
UPD
I found that ALL POST request fails (all forms), while all GET succeeded. Not Sure why fonts fails though.
UPD 2
POST methods work on postman and IE, but fails from Google Chrome.
Version 89.0.4389.114 (Official Build) (64-bit)
UPD 3
2021-04-05 05:44:18 10.129.0.3 POST /profile/edit - 443 user#e.mail xxx.xxx.xxx.xxx Mozilla/5.0+(Windows+NT+10.0;+Win64;+x64)+AppleWebKit/537.36+(KHTML,+like+Gecko)+Chrome/89.0.4389.114+Safari/537.36 https://mymydomain.ru/profile/edit 403 0 0 93
UPD 4
Mime Types and Bindings are also attached
UPD 5
I found that everything works fine if I do request to subdomain, i.e. beta.mydomain.ru rather than mydomain.ru including http:// and https://.
FYI i've issued and tested with two certificates
*.mydomain.ru, mydomain.ru
mydomain.ru (without wildcard)
I after spending lots of hours I gave up fighting this issue. Setup new environment with new certificate and everything is working fine.
Very likely could made a mistake when issues cert first time.