I am currenting developing an NodeJS web application and I am trying to access it with other network FYI my IP is static. but when I am trying to access by company network, I am seeing error 302 FYI I can only see login page but cannot get data from my server but other than this network I can access my application also using HTTP, Does anyone have any suggestion?
Related
I have a react app hosted on AWS as two EC2 instances. One for the frontend(ReactJs) and other for the backend (NodeJs with MongoDB as the database). To put the website behind SSL, the frontend instance is wrapped under an application load balancer. All listeners are configured as per AWS documentation along with setting up the security and target groups.
Route 53 has been also setup to allow all connections to the website to be routed to the https link which is working properly.
Problem arises when I open my website and try to login. When this access is being made from the frontend server to the backend url, the above message is displayed in the Chrome console while in Firefox it gives the following error: "Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at . (Reason: CORS request did not succeed)."
Also just to highlight that the issue is only when i've put the website under an SSL certificate. We have also setup two staging servers which do not have any SSL certificate and there's no issue while doing any activity such as login mentioned above.
Please help me identify where i might be going wrong. I had also raised a technical ticket with AWS support but they have only confirmed that all settings related to the Load balancer and instances etc. are correct and have not been able to find the root cause. I have also tested the UFW for the Ubuntu instance which shows invalid so that is also not an issue.
Thanks,
Pranay
Created a separate application load balancer for the backend instance and then created a cloudfront distribution for this instance. The DNS name of the cloudfront can then be used to access the backend from the frontend.
I have website when accessing it using http, it works perfectly but when i try to access it using https i got error 403 on some resources mainly(images / js )
http://avangardtech.net
https://avangardtech.net
I've mailed the hosting company for this issue and they did not solved it.
i'm using mvc core 3.1 / shared hosting
attached screenshot
I have a node.js based web app which I have hosted in an azure environment as a web service. I am trying to post some data to another server from my webapp to basically store the login details. I am getting an error problem with request: connect EACCES. However I am able to post data using postman to the same server. Any help would be highly appreciated!
From error message, I should add Access Restriction in your app services.
Related post:
EACCESS Error in Node JS
From related post, I think you can Add Access Restriction in your app services.
Our application is making HTTP requests with HttpClient to some websites. In local it always work, but for an unknown reason it fails in production.
Our application is an Azure Website.
We are getting the following error: Unable to connect to the remote server.
We have an IP Based SSL certificate, our IP address is not blacklisted anywhere. It was not happening before 3-4 days.
Depending on the URL we call, it sometimes work, sometimes not, we really don't get why.
UPDATE
It seems to only happen when we make requests to website hosted by GoDaddy, called their support and our IP address is not blocked.
If you isolated that this is not a GoDaddy issue, I would contact support on Azure. It might be a tech issue or networking issue. They will help you isolate the source and fix it.
I am having an issue getting an HttpClient to work from a Windows Azure website. When running the site from my local machine or a local server it is able to connect to the web services without issue. However, once I publish it to Azure it returns a 404 error from the SendAsync method. I would assume a network problem except that if I do a $.getJSON(...) call to the exact same service from the exact same site I get the response back with no issue. I have tried everything I could think of but am currently out of ideas, has anyone experienced anything like this?