Self-hosting - published index.html is blank?

Ask us anything
1

I’ve published my app and downloaded the project files for self-hosting.

When I view the downloaded index.html in a browser (whether directly or as served by aws), it is blank…well there is some html, but nothing is visible.

What is confusing me is that the contents of this file are identical to those on my weweb hosting if a view source on that page …here https://78c679f1-0d75-44b2-8afc-26c2d6cf6700.weweb-preview.io/ This renders fine.

What am I not understanding?

the contents of the index.html are below for reference

:root{ --ww-default-font-family: ‘Plus Jakarta Sans’, sans-serif }:root{–a196b4b3-10eb-45cd-b501-fb0a3f09677f: #08DBAD;
–07d8ed96-d52c-4bf9-9470-3fbc883a81d3: #2B2A28;
–c8153404-8c0f-4957-9b91-e6b7d2751c5e: #006FB9;
–481c1c09-9f7b-4133-af2a-9a6899966ef1: #CDDEEB;
–ca00efd5-bd88-499d-af32-16f2a2b56b1f: #08C49B;
–912aa66a-5b03-4c72-9048-c566105e6e54: #575551;
–d0feb8e1-1767-47e4-8137-10a243394271: #FFFFFF;
–71249384-acc8-4567-9c18-9ef549e6add5: #d74338;
–708835af-5b74-4072-a77e-095712b178b0: #D56058;
–1e377005-b94a-4e2e-816e-4893aa64ec72: #C6C3C3;
–9dece566-b4f7-403b-973d-3a3f85a88ad1: #E8C2BF;
–1b5649d8-3637-4d48-b7ba-5c6d9f1378d8: #DCE4EA;
–c00a7f43-965b-4ec2-9ebc-4e2703cd4b1d: #65B2C3;
–0272f3c6-f5f9-40d7-ac1f-ab07ba08d6d8: #A7FBE9;
–68c6018e-e012-4fea-b030-eb4755ed53bc: #F6F8F8;
–b00d7255-fa6e-47d8-af39-47ff64eb63cc: #1398F1;
–37086fbe-4682-4d89-9586-e6e04ff0563a: #FFFFFF;
–123c25e7-1369-4784-bf3f-da131de77603: #F3C44B;
–47cad190-d6e2-47ed-8ccd-adf84b7f9ce0: #fffe00;
–8c1106d4-0674-4276-9299-3affe4562c46: #ffbf00;
–3d5f274e-700c-4099-9bfd-c8c69a71ab7f: #FF0000;
–d3f6638e-e17e-46b0-b35f-817b20ef3214: #ff8000;
–5a6db73e-ed60-4bc3-b503-5c0de4ab7b80: #08C49B;
–781b7af0-561e-4199-8d06-be3c8146e1a8: #ff4100;}
.ww-app-theme-dark{}We’re sorry but this website doesn’t work properly without JavaScript enabled. Please enable it to continue.
.colHeader {
width: calc(10% - 20px)!important;
border: 10px solid red!important;
}
.blue-bg {
background-color: blue!important;
}
2

same result if I deploy those static files to Vercel

3

weweb needs to load and execute the js files provided with the export in order to render the page. are you sure you correctly uploaded all the other exported assets? it’s easy to check with the browser dev tools on the network tab, look for requests of assets that are not foun

1 Like
4

Thanks for your response. I only see one .js file in what I downloaded from weweb. serviceworker.js Does that seem right?

5

there is a link to a sample project here. you can se both a built and a raw project.

2 Likes
6

so frustrating… I can deploy that test project (to netlify via github) in seconds and it works perfectly.

Either there’s something wrong with how I’m uploading my project to Github or there’s an bug in the exported code or process

7

you can deploy by drag and dropping the folder with the code directly (netlify and also other service allow that). you can try this, just to bypass the github step. If that doesn’t work it may be a problem with the export.

8

Thanks very much…I finally have it working

The issue came in the copying of files by dragging and dropping the folder or select all…the sub folders containing the .js files were not getting copied.

By using the github desktop client, the files all get into the girhub repository fine… I then just deploy that to netflify (or vercel) and all is working.

I think I will make a video of this as I suspect otheres will find the same problem

thanks @dorilama for your ideas and help

1 Like