I recently deployed my application on heroku and I am getting a 502 error with description : HTTP restriction: oversized cookie
Found on Heroku :
Oversized cookies
The cookie in the response will be too large to be used again in a request to the Heroku router or SSL endpoints.
I have no idea on how to overcome this. I tried lots of advices from Heroku troubleshooting page without success.
Also everything works fine locally (setting a Python virtual environment and running foreman start).
Any idea ?
I found the solution by just looking at the response headers locally using Chrome devtools. I realized that Flask sessions are built on top of cookies which caused the oversizing issue (see here). I just got rid of it and now everything works fine.
Related
I added google one-tap to our web app, tested it well working at localhost (see pic).
After deploying to production (react optimized code), the one-tap dialog doesn't show up, checking network traffic, seems some of the requests are missing compared to localhost, but not sure how to diagnose what the root cause is, any help?
(note: I have tried production URL in incognito mode and restarted my browser)
Localhost: (http://localhost:3000)
Production (https://columns.ai)
I’m not sure if it's related to the OAuth scope, but I added the opened and profile scopes, and it's now working in production. However, I can't verify if this is what fixed it.
I am not a backend server guy, mostly work the front end(design and Javascript work). So pardon my beginner questions/terminology. But I could really use some help! Due to covid I am working remote and this is just NOT my expertise.
I have 6 sites I work on locally via a local environment (Nginx, virtual box). Recently, out of nowhere 1 of the sites has started redirecting to an HTTPS version and it will NOT load on any browser due to "ERR_SSL_PROTOCOL_ERROR", so I can not work on that site as of now. All the other sites, that live in the same environment, load fine and are not secure versions.
I have looked at their config files and they are all the same. I don't understand how 1 site is NOW getting redirected to an HTTPS version, I never get into the Ngnix system to change things. And unless I'm missing something it's my local env so nothing could be introduced from the outside.
Questions: Can I just redirect it back to the HTTP version??? OR can I add some certificate to fix my "ERR_SSL_PROTOCOL_ERROR" error?
Any help or direction would be greatly appreciated and the gods will shine upon you.
I'm getting a strange behavior in my stack that I don't know where to look.
Using WordOps default install on Ubuntu 18.04, running on a VM Instance on GCP.
WordOps installed Nginx, php-fpm, MariaDB, WP and Redis cache out-of-the-box.
Initially, everything worked just fine. Then, on my phone, I started getting nginx 404, but on my pc it works. Sometimes the initial page doesn't work, but if I go to wp-admin, the page loads normally.
It is more strange that, on some devices, it works, it others it doenst, returning 404 page.
I really don't know know what's going on.
Anyway, the URL is www.lindastore.co.jp
The problem was with Let's Encrypt SSL certificates. Not sure why, but clearing then re-issuing fixed the problem.
I have a web app that used to run on IIS at http://localhost:3878/Admin; however now for some reason I get this error when I try to access it in a browser:
This site can’t be reached
The connection was reset.
Try:
Checking the connection
Checking the proxy and the firewall
Running Windows Network Diagnostics
ERR_CONNECTION_RESET
Why would I be getting this error all of a sudden when the app worked earlier today? I checked in IIS to make sure the app is started. The IIS logs are not showing any requests to this app. Event Viewer shows a compile error related to this app (I tried to access an include aspx page directly from the browser; I want to fix that issue with the web app where it's displaying the source code from the aspx pages that are used in #include statements) but that shouldn't take the app down once and for all should it?
If someone else face ERR_CONNECTION_RESET with http. Then you could try https first. If https binding fix the problem. It would help narrow down the root cause.
You may need to check whether require https has been enabled or mistake. In some case, enable https or HSTS in project will cause ERR_CONNECTION_RESET.
Of course, enable https would be considered as a workaround.
I have been learning the Laravel framework and I used Laragon to get started. Laragon sets up my web server and my Hosts file so that I can access my work through the browser. Normally, I would boot up the server using the fancy "Start" button in Laragon and then go to the browser and type in "myFirstApp.dev" and my site would show up. Now I am getting an error in the browser that says "This site cannot be reached" (as shown in image1.jpg). How can I fix/diagnose the issue? Has anyone else ran in to this issue?
.
Found the answer to my own question. If anyone runs in to this same issue, here is an explanation. Google released Chrome v63 which forces all .dev domains to https. To fix this either enable SSL in Laragon or chance the domain extension your projects (.test for example). This will require changing your hosts and {Laragon Root}\etc\nginx\sites-enabled files.
https://forum.laragon.org/topic/761/chrome-63-now-forces-dev-domains-to-https/6