I've completely deployed my website with Firebase CLI, and project.firebaseapp.com is accessible and works fine. However, project.web.app keeps showing "Site Not Found".
I'm building my web app with React and already set the folder to "build"
Edit1: I've tried safari, chrome, incognito of both, and also hard refresh and empty cache still showing SITE NOT FOUND.
Edit2: It's working on Line Application Built-in Browser (mobile), but not on Chrome (mobile).
Edit3: Sent the domain to my friends around the world and found out that it's not working for only people living in South East Asia.
As I mentioned in comments, try any other browser. Both the domains are working on my computer. It might just take some time for both to deploy and update the cache.
It's usually better to ask someone who stays far from you and maybe has a different ISP to test update website. I sometimes use Lighthouse and it turns up even it won't show up on my computer. (Apparently the older version gets cached).
I'd recommend disabling cache from network tab in browser console when in development stage:
Related
I am working on a project which is using rails for its backend and react components for its frontend. The app works fine in the Safari browser but for some unknown reason, in the chrome app, it loads the correct path but just renders a white screen showing nothing. If I check the developer tools console, I get to see the following errors
Similarly I refreshed the page and opened the network tab in developers tool and got to realise that some of the packages have not been downloaded.
The point to note is that the app also requires a certificate for running it locally and I have already downloaded that certificate and trusted it so it should also not be a problem. I am stuck at it for a really long time. Can anyone tell me the solution?
As the app works fine in safari, I don't think its related to code but its just a guess. So far I have tried disabling all the extension as well as clearing the browser data but haven't been able to see any progress...
I made a PWA (progressive web app) a few weeks ago with React and some PWA configuration. From that moment, the name I gave the app still displays in the top bar when I try to run any other app on localhost:3000.
Apart from this, there were no issues with running applications on localhost:3000 for a long time, so it didn't bother me. But since last week, when I tried starting my React app (yarn start) on port 3000, my app won't render anymore.
I figured it might have something to do with the browser's cache settings, so I tried opening the app in another browser and it suddenly worked.
Notice that the name has now changed back to "React App" instead of the PWA name. Since it worked on the other browser I started testing some routes and tried to delete my cache in the browsers I normally use.
I tried adding something to the route (for example: localhost:3000/test) and this also redirected me to the right page (from the right application).
Is my PWA running somewhere in the background and causing issues or is there some browser configuration I am not setting right?
It is probably cache, it's not possible to run two apps under same port at the same time (at least by default).
You should have set that cache shouldn't work on dev environment to prevent that happening.
You can try incognito or open dev tools in Chrome => right click on refresh icon and select "Empty cache and hard reload".
Also try unregistering service worker in your app or in browser dev tools.
A way good way to resolve this error is -
Right-click and press inspect element to open the dev tools.
Under the dev tools, head on to the "Application" tab.
Here, on the left side, you'll find an option "Service Worker".
Click on it, and from the left side, press unregister.
After this, you can press "Empty Cache & Hard Reload" and your application would work just fine.
Empty cache and hard reload
you should press Ctrl + F5 together
I created an app in Java in Eclipse on Google App Engine. For about a year now, I've had that app embedded in a google site iframe as a gadget. I added it using the "add gadget by URL" option and put in the URL of the app: https://mycompany-helpdesk.appspot.com (where mycompany is my company's actual name).
This has been working flawlessly for about a year. Recently I made a small change to the Java code, and it seemed like about a week after that change, the app will not display in Google sites anymore.
The app works just fine if I navigate straight to its URL https://mycompany-helpdesk.appspot.com.
I removed the gadget iframe on my google site and then tried to add it back, but the error I'm getting now is:
The gadget you added is not valid
Unsupported feature: org.apache.shindig.common.xml.XmlException: The markup in the document preceding the root element must be well-formed. At: (1,3)
I have a couple of these apps and I tried using the other one, but I get the same error. I've tried to add them on other google sites and even created a fresh one and still get the same error. I've spent days googling this but I don't think I've found anything that applies to my situation.
Did something change where suddenly it is not possible to do this anymore? If I can't embed the app this way any more, does anyone know of another way that I might be able to do this?
UPDATE: When I am editing the site, under Insert > More gadgets, if, instead of using the "Add Gadget by URL" link (which is what I've been using to insert this gadget) I use the "Include gadget (iframe)" gadget developed by Scott Johnston, then my apps will appear in Firefox and Safari, but not Chrome. This is not useful to me as our employees primarily use Chrome.
I think I'm just going to abandon Google Sites and redo the page in GAE. Hope this helps someone else who has been banging their head against their desk as I have been.
Update: I noticed that suddenly all the embedded apps on my test pages were working, so I reverted to an old version of the google site where the app was still embedded. Voila, it works again. Now if I can just figure out how to add in another embedded app I'll be good to go. It had been working in Safari and Firefox but that doesn't seem to be working now...
I've built a web app on a MEAN stack (Mongo, Express, Angular, Node) and I run it through Heroku. When I access the application on my computer through Google Chrome everything works great (although rather slowly). However, when I access the application on my iPhone through mobile Safari barely anything works. Links on the home page only appear sometimes, nothing appears on the sub pages.
The app lives at http://mobseen.it
Any idea why Chrome would work well but mobile Safari would work so poorly, and what I could do to fix this?
I've surfed your site from both my computer and my phone(which worked fine albeit a bit slow). After analyzing it briefly in Chrome as well as pingdom, I think you're problems are coming from the amount of resources the device is pulling in and processing. Take a look at some of the recommendations on pingdom and go from there.
I would also try setting it up on OpenShift to see if it's any better.
I'm a beginner with DotNetNuke and am having trouble debugging this problem. We are using DNN version 5.
On our local development machines our DNN site renders just fine. But we recently deployed to our test server and on there the site only renders fine when logged in as the Host. When viewing the site as just a normal visitor, all the styles are messed up -- it is just a white page with images gone and menus stacked vertically.
Clues / Notes:
We recently added a new .ascx and module
There are javascript errors, but it hard to tell what is causing them
You may ask about the Log Viewer screen. I looked there and I see exceptions, but I think the exceptions there are unrelated ( will look into this)
Works fine in our local dev environment
In server, only renders fine when logged on as Host
What are some steps I can take to try to debug this? Where else can I look besides the Event Viewer to see what is going on here?
Thanks!
What is the "new .ascx" that you deployed? Is that a skin page?
If something is wrong in the skin page and it is the default site page (under Admin > Site Settings), that would explain why non-admin users have issues, but Admin/Host users (where the site's Edit skin is working) don't have issues.
This solved it:
https://stackoverflow.com/a/3831419/614263
Due to permission settings it looks like IIS was blocking requests from the root to javascripts and css files. When looking at the Network traffic in FireFox I noticed that 404 errors were coming from "login.aspx?ReturnURL=../../blahblah.css"
Thanks for all your help and suggestions.