I have an issue on fortrabbit which I can't figure out on my own, and google is not of much help either.
I have this website which works fine on the temp domain that fortrabbit gives upon creating the app: App on Dev. Now I have an actual domain for this which is: App on Live, but it shows a 404 page for some reason. The app is configured in fortrabbit to point to the 'public' folder and overall has the same setup as the Dev app, but I still can't figure out why it shows a 404 page.
Thank you!
Found the fix for this. The domain in fortrabbit dashboard had to be set to "www.blackflame.digital", it was set to "blackflame.digital" before, so just had to add the "www" at the beginning.
Related
I've worked on a html/css for a website based on a theme. It works well on other websites and when I open the index/website in my browsers. But once uploaded to my hosting the first image (intro__bg) doesn't load. Everything else including other images work well though.
Can anyone see how to fix this??
(http://test.ar-cs.co/)
thanks!
/A
I've treid reaching out to my hosting but they were of no help.
The resource http://test.ar-cs.co/images/intro-bg.jpg gives a 403 error meaning access is denied. You probably need to change the permission of the file with chmod 775 images/intro-bg.jpg or configure your web server to allow requests to the images folder.
I made github pages site with a custom domain.
It runs in Tor and Safari but I get "This site can’t be reached" message trying to run it in Chrome and some other browsers, what could be wrong?
The repository is public, cache is cleaned.
There was a problem in C:\Windows\System32\drivers\etc\hosts file where my domain name was pointed to localhost
the file was changed probably probably due to my attempts to host the site on a laptop
After some experiments with PWA I've encountered a strange issue with Google Chrome only. Every other browser works just fine.
When I load http://localhost the response is: "This site can’t be reached"
The error status is: "ERR_FAILED" (404)
Note:
"ping localhost" returns 127.0.0.1 (as it should be).
wget -qO - 'http://localhost' loads the correct content in terminal.
every other browser loads the correct content.
the setting in /etc/hosts leads to 127.0.0.1
if I access the content via IP (127.0.0.1) it loads just fine.
I have cleared the browsing cache
the PWA cache seems to be clean.
The offline box in the network tab is not checked.
If anyone has any ideas on what could cause the issue please share.
The only clue I have is that in the sources tab of the code inspector
there's the content of sw.js (my service worker) but there's nothing to do with it.
I came out that the issue was caused by a cookie called ServiceWorker.
After deleting it everything works fine.
Im trying to deploy my WebApplication on a TomCat 9.0.11.
Now everything went good so far, the artifact was deployed into the ROOT directory, but the page just wont load, and doesnt shows up my index.html? Does anybody see the error here? If i forgot something please tell me so i can add the missing stuff.
EDIT: I want to run the server on Windows first, later on Debian. The website should also be accesibile trough example.com not f.e. example.com/app (or for Windows localhost not localhost/app)
TomcatConfiguration1
TomcatConfiguration2
Artifacts
ServerLog
TomcatServer after deployment
Trying to open the page
Greets
Lukas
i think project should be inside the webapp folder not inside root .Please attach log which can show us the context loading .
Or you can refer to this link:
Deploying just HTML, CSS webpage to Tomcat
I'm new to polymer. I followed the starter kit and created some pages. On my PC localhost, everything works fine. But once deployed to the server, I've got the following problem :
- I can access the site
- I can navigate between my different pages
- but if I try to access directly to a page or if I actualize my browser page when navigating : I get a 404
I don't underdstand why.
Do you have any idea ?
my case : www.tora-photo.com -> works
http://tora-photo.com/gallery/mist -> 404 but can be accessed from the previous url
thanks a lot for your help
the solution : use use-hash-as-path in app-location and add hash to href source
Your server needs to redirect all paths to your index.html which is actually handling your routing. The server is returning a 404 because you don't hactually have a file file called index.html in the /gallery/mist/ folder from the root of your web servers base.