Hi,
is the Wiki-site temporarily down?
greetings
damir
Size:
Color:
Hi,
Yes and will stay so until a solution is found - for at least a few days. Sorry for the inconvenience.
Size:
Color:
The Wiki is back up. Our apologies for the delay in restoring functionality!
Size:
Color:
Is WIKI down?
Size:
Color:
Size:
Color:
I didn't navigate directly. I followed a (bad?) link from another WealthLab page. No, I don't know which. EDIT: Actually, the link to "Wealth-Lab Wiki" at the top of this page is
https://www.wealth-lab.com/Wiki/.
Size:
Color:
Thanks, we know. We're going to make that link at the top of the page open in a new tab soon.
Size:
Color:
UPDATE: the Wiki link now opens it in a new tab.
Size:
Color:
I have not been able to access the WIKI site for a few days.
Is the WIKI site still working?
Size:
Color:
Size:
Color:
Hi, Eugene:
It works on IE and Firefox, using the http:// prefix (but not with the https:// prefix).
It doesn´t work in Chrome even when all the Site Preferences has been deleted. At least my chrome browser always forces the https:// prefix.
When using https a privacy error message saying that the site certificate has problems is shown. The error code is "NET::ERR_CERT_COMMON_NAME_INVALID"
Size:
Color:
Size:
Color:
Thanx, Eugene.
It works perfecly now from Chrome.
Size:
Color:
Carlos, no hay de que.
P.S. I thought about adding this advice to the Wiki FAQ but who's to see it if the Wiki couldn't be opened? ;)
Size:
Color:
Hi
I'm trying to read www2.wealth-lab.com/WL5WIKI/FillSeriesFromFile.ashx, referred to in many forum articles, but I haven't been able to reach https://www2.wealth-lab.com/ in Safari, Chrome or Firefox for days. I've tried https and http. I typically get that the server didn't respond or timed out. Is there something wrong at my end, or a new URL?
Thanks
Nick
Size:
Color:
Hi Nick,
At your end. For Chrome, please check out my post #6 here:
Source code for VKW Bands?. For Chrome, solution is in post #12 above.
Size:
Color:
Size:
Color:
Is there a solution for Edge?
Size:
Color:
We never investigated but nowadays Edge is Chromium-based so I guess the Chrome solution should apply.
Size:
Color:
QUOTE:
We never investigated but nowadays Edge is Chromium-based so I guess the Chrome solution should apply.
I had to download the new Edge Browser (2020) which is the Chromium-based one. It did have a similar command as Chrome to get to where you can delete the domain:
edge://net-internals/#hstsAt first it seems I got it to work, but now I can't get it to work anymore. Even on Chrome, it seems like I have to clear browsing data each time I reopen Chrome.
This security stuff, as you know, is getting very serious and restrictive. I wonder if one day soon there will be no workaround. Is there a plan to migrate the Wiki content, if not the Wiki itself, to an SSL based site?
Size:
Color:
There is no plan to migrate the Wiki. Sorry I don't have experience with the new Edge with its 2% market share. Please try Firefox, it works with said tweak without issues.
As the forum doesn't support sticky posts, I duplicate the important information from post #17 below:
Let's address the problem reports about the Wiki being down which we've been getting in email and tickets lately.
The Wiki is not down. Your browser is trying to connect to HTTPS whereas the Wiki is HTTP-only legacy. Apply a workaround below to www2.wealth-lab.com (NOT www.wealth-lab.com which supports SSL.)Chrome:
Make Chrome stop redirect from http to httpsHow to stop an automatic redirect from “http://” to “https://” in ChromeFirefox:Firefox redirects to https
Size:
Color:
I just got bit by this today after having things working great for weeks. And it certainly isn't a trivial workaround.
Can I ask why this isn't fixed properly. The site appears to be already enabled for SSL, it just needs a valid certificate. Free certificates are available: https://letsencrypt.org/ and should only take a few minutes of effort to request, obtain, and install.
I always tell people to NEVER enter a password into a site that is not SSL enabled because without encryption it is trivial to sniff your password in transit... it is literally in plain text. I sure hope no one who uses the Wiki is using the same username/password they use for other sites.
PLEASE fix this properly... there is very good reason modern browsers are defaulting to SSL, and eventually the workarounds suggested above will stop working.
Size:
Color:
The Wiki is not our SSL enabled website. It's legacy technology that does not support HTTPS and runs on its own domain (hence the "www2"). Upgrading it is not an option so it's good as long as the workaround lasts. There are good reasons to maintain it as is: link preservation, convenience, security (no successful hacker attack in over a decade despite ongoing attempts) etc.
From my point of view, this browser cruzade against HTTP is a bit too much. If required by law or contract we will rather choose to host the protected content (such as API docs and source code) elsewhere and disable Wiki registrations altogether.
Size:
Color:
Size:
Color: