This app is built using umijs and antdesign pro for frontend and node js express server for backend hosted on a Ubuntu server and Cloudflare is used for DNS management.
If the app is being loaded for the first time on any browser, it works as intended. But if we refresh it, it gets stuck on loading and outputs this specific problem:
for chrome:
for firefox
The app is then only re-usable after purging cache (Cloudflare) and then persists again when refreshing. The problem does not exist when using "serve" and serving the files locally.
This issue produces by a service-worker. try without service-worker.
Related
I have a simple quarkus api app. I've tested the app on my local machine and its running fine. But when i try to run the same app in windows server it starts perfect but does not respond to any of my api request. It is not showing any error or problems. I've tried multiple ways to run the app also through package and jar files but all led to same result. screenshot of the palce where app gets stuck
Currently working on a project and everything was working fine. Then suddenly after rebooting from a power cut whilst working on said project, the electron application has since failed to load any online resources. It works perfectly fine when on a native browser using localhost but will fail to load any online resources on the electron application version.
Initially, I thought it was a firewall issue but changing settings has not changed anything. I've reset router/pc multiple times to no avail.
The error recieved for any online resource is GET [URL] net::ERR_EMPTY_RESPONSE
Edit: Here is a screenshot of the error displayed in electron:
Used auth0 for my react project and it works fine at my local.
When i put my project to the server login page shows up, but after i try to login i get an error.
http://localhost:3000/callback?code=ZSaQ96OshsFfpBUN&state=q3KiPGbEPtIZ3UuSLd.KSbKjdXqk9-pD
firefox says
unable to connect - cant establish a connection to localhost:3000 and on
chrome i got
this site can't be reached - localhost refused to connect
I tried different callback urls on the auth0 side but nothing changed. I do not know exactly what to do actually
It looks like your project isn't running on the same connection that you were locally. Make sure to change all the registered callbacks to their current locations when changing to a different deployment.
When opening some web pages in Safari (iOS - CMS website hosted in a Apache server) it shows the following message.
Tried to remove all scripts from the page and it doesn't worked
Checked Apache access log and none on the requests were logged in access log
Checked Apache error log and no errors are logged
Tried lot of methods to figure it out (technically and logically). Anyone experienced the same issue?
If none of your requests are being logged, then your client isn't getting through and you have a problem outside of your application scope (like a network connectivity or firewall issue)
I have been trying to come up with a solution for my website to play nicely with socket.io. Right now I have apache serving my website (mostly in php) and I am trying to implement a live chat support feature using socket.io (node). I am able to get the chat functionality working separately (using express and going to wundertutor.com:8000) but when I just go to wundertutor.com (where the chat functionality is included as well), I am getting issues with CORS (Cross-origin resource sharing). Here is my error (on the client side):
XMLHttpRequest cannot load http://chat.wundertutor.com/socket.io/1/?t=1356421805823. Origin http://wundertutor.com is not allowed by Access-Control-Allow-Origin.
OR
XMLHttpRequest cannot load http://chat.wundertutor.com/socket.io/1/?t=1356422229000. Cannot use wildcard in Access-Control-Allow-Origin when credentials flag is true.
depending on wether I include this line of code in my app.js
io.set("origins","http://wundertutor.com");
Basically, I just want my node app to be a suppliment to my main site, but I really don't know where to specify the CORS parameters. I have tried doing this in my .htaccess file, in app.js, as well as in the client javascript, none of which have proved successful.
(Also, another thing I find strange is that when I go to wundertutor.com:8000, my node app correctly opens up a websocket, but when I try to go to wundertutor.com, it tries to use XHR polling which ends up causing this CORS mess)
Any suggestions would really be appreciated!
I figured out my problem if anyone else is experiencing the same issue. While I still think that what I am trying to do is using CORS, I didn't have to do any specific setting of Access-Allow-Origin-Control on either the Apache or node.js side. What I did to fix my problem was to serve the socket.io javascript file from the node.js server as opposed to the apache server. This made the requests coming from the socket.io javascript file have the same origin as where the javascript file was loaded. Here is an example:
<script src="http://wundertutor.com:8000/socket.io/socket.io.js"> </script>
(node server - correct)
vs
<script src="/javascripts/socket.io.js"></script>
(apache server - wrong)