Error loading index html

Replicated site gives: Error loading user ‘index.html.var’

If you are getting this red error:
Error loading user ‘index.html.var’
instead of a replicated site, the problem is that the affiliate parameter is missing. This can happen e.g. in case when you use the «custom location» setting for the site replication and you use the same URL for your main site. So usually you access your site here: https://yoursite.com/ and you have also set this as the custom location for the site replication, so your affiliates has links looking like this: https://yoursite.com/testaff

The code at your server (.htaccess code) makes the replication to work — it reads the referral ID behind https://yoursite.com/ and creates the replicated site, so in this case, it would be «testaff» whose site will be displayed. So when there is nothing after https://yoursite.com/ there is actually something hidden in the browser — index.html and this is read by .htaccess code as index.html.var because it thinks this is an affiliate (referral ID), sends it to the replication script and the script returns the error because there is no affiliate with referral ID index.html.var .

To fix this problem, you have to modify your .htaccess code a little. Add these lines below line «RewriteEngine on» in your .htaccess code:

RewriteCond % !-d RewriteCond % !-f RewriteRule ^index.html.var$ https://www.yoursite.com/PAP4_directory_name/scripts/page.php?a_aid=general_affiliate_ID_Here&a_bid=replication_ID_here&a_redir=Y [L,P,QSA]

RewriteCond % !-d RewriteCond % !-f RewriteRule ^index.html.var$ https://www.yoursite.com/index.html [L,P,QSA]

Источник

How to Fix Error Loading Index.html 404 [object%20HTMLElement]

If you have encountered the error «Error Loading Index.html 404 [object%20HTMLElement]» while trying to access a website, then you know how frustrating it can be. This error message means that the website you are trying to access cannot be found on the server. But, fortunately, there are some ways to fix this error. In this article, we will provide you with some methods to fix the error.

Check the URL

The first thing you should do is to check the URL you typed to access the website. It could be possible that you have misspelled the URL or missed out on a character. Check the spelling, capitalization, and any special characters that are required in the URL.

Reload the Website

Sometimes, the 404 error is just a temporary issue caused by internet connectivity problems or a server error. In such cases, reloading the website can fix the error. Click on the reload button on your browser or press F5 to refresh the website.

Clear Browser Cache

If there is a problem with your browser’s cache or cookies, then it could be causing the error. Try clearing your browser’s cache and cookies and then reload the website. Here is how you can do it for different browsers:

• Google Chrome: In the menu, click «More Tools» > «Clear browsing data.» Select the time range and the data you want to clear and click «Clear data.»
• Mozilla Firefox: In the menu, click «Preferences» > «Privacy & Security.» Scroll down to the «Cookies and Site Data» section and click «Clear Data» > «Clear.»
• Safari: In the menu, click «Safari» > «Preferences» > «Privacy.» Click «Manage Website Data» > «Remove All.»

Try a Different Browser

If the error still persists, try accessing the website from a different browser. This will help you confirm if the issue is with your primary browser.

Contact the Website’s Webmaster

If all the above methods fail, then it’s time to contact the website’s webmaster. Explain to them the issue you are facing and provide them with the URL and the steps you took to fix the error. They may be able to provide you with a solution or fix the issue from their end.

In conclusion, the «Error Loading Index.html 404 [object%20HTMLElement]» error is a common issue that can be fixed using the methods mentioned above. Ensure that you check the URL, clear the browser cache, try a different browser and contact the website’s webmaster to resolve the error.

Источник

Saved searches

Use saved searches to filter your results more quickly

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error loading index.html #67

Error loading index.html #67

Comments

I get the error Not allowed to load local resource when trying to load the index.html .

My file structure is resources/app containing my index.html and the static directory.

I declare the homepage in my boostrapper with Homepage: «index.html»

I’d appreciate any help resolving this.

The text was updated successfully, but these errors were encountered:

Running macOS High Sierra so it’ll be darwin/x86.

The issue that’s causing it is my resources file isn’t being packaged into the exe.

The important line in the logs is:

However when I navigate to the exe directory, there is only a folder called my application name and a folder called vendor, no resources folder.

@connorlurring are you using the bundler and the bootstrap? If so can you provide:

• your folders structure
• the content of your bundler.json
• the first lines of the log when you run your app with the -v flag

< "app_name": "Samurai", "output_path": "output" >

├── resources │ └── app │ ├── index.html │ └── static │ ├── css │ │ └── style.css │ ├── img │ └── js ├── vendor │ ├── astilectron │ │ ├── LICENSE │ │ ├── main.js │ │ ├── package.json │ │ ├── readme.md │ │ └── src │ │ ├── client.js │ │ └── consts.js │ ├── astilectron-v0.14.0.zip │ └── status.json └── vendor_astilectron_bundler ├── astilectron.zip └── electron.zip 

DEBU[0000] Starting. DEBU[0000] Provisioning. DEBU[0000] Provisioning Astilectron. DEBU[0000] Removing directory /var/folders/42/4k7bfr3j6dz5__ydtksvbxth0000gn/T/go-build573977524/command-line-arguments/_obj/exe/vendor/astilectron DEBU[0000] Downloading https://github.com/asticode/astilectron/archive/v0.14.0.zip into /var/folders/42/4k7bfr3j6dz5__ydtksvbxth0000gn/T/go-build573977524/command-line-arguments/_obj/exe/vendor/astilectron-v0.14.0.zip DEBU[0001] Creating directory /var/folders/42/4k7bfr3j6dz5__ydtksvbxth0000gn/T/go-build573977524/command-line-arguments/_obj/exe/vendor/astilectron DEBU[0001] Unzipping /var/folders/42/4k7bfr3j6dz5__ydtksvbxth0000gn/T/go-build573977524/command-line-arguments/_obj/exe/vendor/astilectron-v0.14.0.zip/astilectron-0.14.0 into /var/folders/42/4k7bfr3j6dz5__ydtksvbxth0000gn/T/go-build573977524/command-line-arguments/_obj/exe/vendor/astilectron DEBU[0001] Provisioning Electron. DEBU[0001] Removing directory /var/folders/42/4k7bfr3j6dz5__ydtksvbxth0000gn/T/go-build573977524/command-line-arguments/_obj/exe/vendor/electron-darwin-amd64 DEBU[0001] Downloading https://github.com/electron/electron/releases/download/v1.8.1/electron-v1.8.1-darwin-x64.zip into /var/folders/42/4k7bfr3j6dz5__ydtksvbxth0000gn/T/go-build573977524/command-line-arguments/_obj/exe/vendor/electron-darwin-amd64-v1.8.1.zip 

Ok so I managed to resolve this.

GoLand was saying that Asset and RestoreAssets didn’t exist (due to the nature of how the binds are generated). For this reason I removed them hoping that the library would fall back to default (the default folder structure). It appears that it does not and, as such, there was no ability to load the application due to the lack of access to assets.

I propose that when the Asset and RestoreAssets aren’t specified the OS bindings are used as default as these are optional in the struct and shouldn’t be required unless the user wishes to implement custom behaviour.

@connorlurring good to know you managed to resolve this 🙂

Unfortunately, what you’re proposing is not possible. Indeed embedding assets in the binary happens at build time. At runtime, if you haven’t specified an Asset or a RestoreAssets function, there’s no way GO knows which function to execute to disembed your asset. You have to specify it at build time. There’s no such things as OS bindings or I misunderstood what you meant by it.

If you don’t specify those bootstrap options, the assumption is made that your resources files are already on disk and don’t need to be disembedded.

Источник