I have "kubertinirize" a few images like the "Apicurio" which seems to work nice on Azure Kubernetes Cluster.
Then when I hit the link http:///apis/registry/v2/search/artifacts?limit=10&order=asc&orderby=name
Sometimes I get proper result:
{"artifacts":[],"count":0}
Some times I do not get proper result:
HTTP ERROR 404 Not Found
This happens also to the rest of the pages like the UI page and therefore the services which are using it cannot communicate with Apicurio all the time.
Notice that same docker image running in docker engine on my local pc is working without any issue like this one.
Any ideas?
Related
Setup Overview
I have setup on GCP a Kubernetes cluster last week (1.15.12-gke.2) using the latest nginx-ingress helm chart (App version: 0.34.1, Chart Version: ingress-nginx-2.12.1)
For the website I made a basic echoheader deployment exposing the app via an ingress object configured with the force-ssl-redirect=true annotation.
Symptom
When visiting the site with IE11 on Windows 8.1 (It has to be explicitly this version) then I get a "This page can’t be displayed" message.
Even when I implement the fix from this Github issue into the environment I will still get the same issue. The picture is the same error for http or https.
Does anybody have an idea how I can debug or solve this? I am right now stuck without any idea how to further Analyse the problem.
Just kill the default RC4+RSA ssl cipher and it's saul goodman
Use this
nginx.ingress.kubernetes.io/ssl-ciphers: "ALL:!aNULL:!EXPORT56:+HIGH:+MEDIUM:+LOW:+SSLv2:+EXP"
Works fine for me
It's not accepted by Internet Explorer anymore https://support.microsoft.com/help/3151631/rc4-cipher-is-no-longer-supported-in-internet-explorer-11-or-microsoft
Source right here https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/annotations/#ssl-ciphers
Enjoy
I am trying to deploy my MERN stack application to a server using AWS-EC2. Though everything seems to be working when I try and make API calls I get weird non-json returns which destroys all functionality.
I think I read that the reason this may be happening is that Nginx doesn't work with static pages, but when I tried using the non-static page (client/public/index.html as opposed to client/build/index.html), the page just renders black, and the inspecting element shows there is nothing in the body.
Is there any workaround or alternative solution?
Here is what the API returns using the server port created with Nginx:
Here is it working perfectly fine locally on my machine:
I am new to web development and even though i have looked around I am still stuck with this part which is to manage to make my api run on a server. Locally it runs perfectly but once I add my api inside my server it just says not found whenever i attempt to access it.
This is the folder structure
-www
--wp-admin
--wp-content
--wp-includes
--ProjectApi
---app
---bootstrap
---config
---database
---public
----index.php
----.htaccess
---resources
---routes
---storage
---tests
---vendor
Locally i would just say http://localhost/ProjectApi/public/api/v1/hello and this would call my api and do its function. But once it was added to the server when i do http://randomServerName.com/ProjectApi/public/api/v1/hello It just gives me a 404 not found error.
I am not sure what happened because everything was working fine but now there is a weird bug on my app.
I had an app hosted on Modulus at www.raiseyourflag.com
I then created a version of it in React and Moved it to DigitalOcean at react.raiseyourflag.com to test and everything was working fine (all I did was import the Modulus DB into Compose.io)
Then I changed the nginx config to point to www.raiseyourflag.com and changed the DNS for www to point to the DO droplet and now all the images are getting a 404 but when I do something like CareerImages.findOne(); I get an Object and if I do CareerImages.findOne().url({stores: 'careerLargeImages'}) I get the url but when I go to it, I get a 404.
Is there any additional setup I should be performing on nginx to set so that /cfs files work.
I am using S3.
Also, now on localhost i get http://localhost:3000/cfs/files/careerImages/MoaFx95kSuZ3yTDvX/choreographer.jpg?store=largeCareerImages net::ERR_CONTENT_LENGTH_MISMATCH which wasn't happening before either :/
I have a website hosted at webhost4life.com. It works fine when I load up the website from various locations (home, coffee shop, library, etc). But from my friend's house it will NOT load. It just looks like it's sitting there thinking and the website might load a few images here and there but that's. The full page doesn't load and most of the time nothing loads.
This is a c# asp.net website. My question is, how do i go about troubleshooting to find out what is wrong?
Right now I do not really know where to start. These are the things I have tried:
static page - i uploaded a static html page and that loads up fine!
fiddler - i track the session in fiddler and get nothing back. but when i try the static page i get normal results and it's working fine.
tracert www.mydomain.com - this looks fine, i get similar results with www.yahoo.com
telnet www.mydomain.com 80 - i do this to ping port 80 of the website. if i type "get" and hit enter i see a "Bad request" message but i see the same message for other websites and they work fine from here
ftp - ftp works fast and is fine
So at this point, I know that my asp.net parts of the website doesn't seem to work but only from this one location. It works fine from everywhere else I have tried. But static pages DO work just fine.
Any ideas?
Try doing the telnet 'get' and actually request a page that is having problems. It could be that you are referencing elements in your application that your friend's computer is having trouble connecting to. If you get back all the mark up of the page, then it's one of the items that the page is referencing that is causing the problem. If the page renders incompletely, then your site may be having problems or the might be a network issue between your friend's house and your site. Since your application loads up from other locations I'd suspect that your friend's computer or network has the problem rather than your site. Your site shouldn't care where the request is coming from.