Ok, that's fair enough.
@girish said in No 'resetToken' for admin password reset:
But as you figured you can just put a json in that ghost file /home/yellowtent/platformdata/cloudron_ghost.json and that's it:
{"username": "sometemporarypassword" }
However, this might be worth adding to the documentation.
Hi,
I've just attempted to purchase a Cloudron subscription. I'm doing it on behalf of a co-operative company I am a member of. The company has a bank account but does not have a credit card, so I attempted to use my own for now, however, I only have debit cards, and none of mine seem to work. The subscription form says "Your card does not support this type of purchase" for one, and "Your card cannot be charged" for the other.
Is this really the only way to pay, and if so, are there any plans to allow anything else in the immediate future? As it is this is an unexpected show-stopper for our use of Cloudron.
@Hillside502 I was trying using my personal Halifax debit card, on a UK account. It was unclear if it's a problem with my card specifically or the bank...
The company I'm paying on behalf of has a bank account but no credit card, I'm not sure if it has a debit card, will find out.
@yusf Oh. Doh. Thanks.
So I've worked around this by telling Firefox to "Forget this host" (right-click on an URL to get this option in the history tab), and thereby got to the web console that way.
However, it could still be handy to know how to trigger the renewal from the terminal, as this might not be the only case when you'd need to do it.
Rereading, could be worth noting for other readers of this thread: the poll2 plug-in (which seems to be marked as possibly not working with this version of NodeBB) is not the same as the poll plug-in (which seems to be marked as working)/ I'm not sure why I had both installed.
Rereading, could be worth noting for other readers of this thread: the poll2 plug-in (which seems to be marked as possibly not working with this version of NodeBB) is not the same as the poll plug-in (which seems to be marked as working)/ I'm not sure why I had both installed.
After disabling all the plugins and rebuilding, there is just this error:
Failed to load ‘https://forum.code-operative.co.uk/assets/vendor/fontawesome/fonts/fontawesome-webfont.woff2?v=4.7.0’. A ServiceWorker intercepted the request and encountered an unexpected error.
Re-enabling these plug-ins:
Then I see 404s on /plugins/nodebb-plugin-markdown/styles/railscasts.css. Seems to be a bug in the markdown plugin, I filed a bug here:
I also get more occasional .ttf//.woff errors as above. And lots of [benchmark] warnings in the server logs, I think these can be ignored.
Renabling these seem to go without faults:
However, nodebb-plugin-private-forum introduces errors, when visiting anonymously.
https://github.com/LM1LC3N7/nodebb-plugin-private-forum/issues/2
Finally, installing nodebb-plugin-poll doesn't (so far) seem to create any errors....
Will keep an eye on things. There were some other plug-ins (code-button, emoji-related) which I didn't consider important enough to re-enable.
I'm trying to disable plugins and will report back.
Should the NodeBB Cloudron package version (v1.17.0-1) match that reported by NodeBB itself (v1.16.0)?
The installed plugins:
# ./nodebb plugins
Active plugins:
* nodebb-plugin-code-button (installed, enabled)
* nodebb-plugin-composer-default (installed, enabled)
* nodebb-plugin-dbsearch (installed, enabled)
* nodebb-plugin-discord-bot (installed, enabled)
* nodebb-plugin-discord-notification (installed, enabled)
* nodebb-plugin-emoji (installed, enabled)
* nodebb-plugin-emoji-android (installed, enabled)
* nodebb-plugin-markdown (installed, enabled)
* nodebb-plugin-mentions (installed, enabled)
* nodebb-plugin-poll (installed, enabled)
* nodebb-plugin-poll2 (installed, enabled)
* nodebb-plugin-private-forum (installed, enabled)
* nodebb-plugin-soundpack-default (installed, disabled)
* nodebb-plugin-spam-be-gone (installed, disabled)
* nodebb-rewards-essentials (installed, enabled)
* nodebb-theme-lavender (installed, enabled)
* nodebb-theme-persona (installed, disabled)
* nodebb-theme-slick (installed, disabled)
* nodebb-theme-vanilla (installed, disabled)
* nodebb-widget-essentials (installed, enabled)
No, that still doesn't resolve the problems. The console shows these errors again on first visit, following erasing the browser information for the forum domain:
This page uses the non standard property “zoom”. Consider using calc() in the relevant property values, or using “transform” along with “transform-origin: 0 0”. [...]
Uncaught TypeError: t is not a function
<anonymous> serializer.js:17
<anonymous> serializer.js:162
serializer.js:17:25
Loading failed for the <script> with source “[...]/assets/src/modules/bootbox.js?v=1mjvdi86tsu”. [...]:1:1
Uncaught Error: Script error for "bootbox", needed by: forum/category/tools
https://requirejs.org/docs/errors.html#scripterror
makeError require.js:168
onScriptError require.js:1738
require.js:168:16
ServiceWorker registration failed: DOMException: The operation is insecure. app.js:793:13
Loading failed for the <script> with source “[...]/assets/src/modules/timeago/jquery.timeago.js?v=1mjvdi86tsu”. forum.code-operative.co.uk:1:1
Uncaught Error: Script error for "timeago/jquery.timeago"
https://requirejs.org/docs/errors.html#scripterror
makeError require.js:168
onScriptError require.js:1738
require.js:168:16
@girish I've tried the rebuild and restart several times. It did rectify some other problems we were having, but these seem to be persistent.
But I'll try it again, just in case. I'll list the plugins after it starts again.
We have semi-intermittent problems using NodeBB. These come in more than one form - they may have the same cause? There seem to be components missing.
The kind of problems I've noticed are loosely as follows.
/service-worker.js?loggedin=true)serialiser.js within the poll module)require.jsRecently, having seen the raw javascript page, my subsequent attempts to log in either have no visible effect - I remain on the log-in page - or I get taken to a blank page in a new tab with just the word "Forbidden" (the URL path for this page is /login).
The missing components and the related errors can be seen all over the site, causing problems.
There seems to be some state to these problems. Telling my browser to forget all state about the site helps reset it such that I can log in, but does not eliminate these problems.
Inspecting the network tab in the browser console I see "404 not found" errors for the following components:
/plugins/nodebb-plugin-markdown/styles/railscasts.css/assets/src/modules/bootbox.js?v=ohhorhrib2o/assets/src/modules/timeago/jquery.timeago.js?v=ohhorhrib2oThese seem to explain some of the errors in the console. However, I can't tell why these files are absent, and neither using the rebuild-and-restart option or the cloudron restart service option seem to rectify it.
Uncaught TypeError: t is not a function
<anonymous> serializer.js:17
<anonymous> serializer.js:162
serializer.js:17:25
Loading failed for the <script> with source “https://forum.code-operative.co.uk/assets/src/modules/bootbox.js?v=ohhorhrib2o”. login:1:1
Uncaught Error: Script error for "bootbox", needed by: forum/category/tools
https://requirejs.org/docs/errors.html#scripterror
makeError require.js:168
onScriptError require.js:1738
load require.js:1943
load require.js:1685
load require.js:834
fetch require.js:824
check require.js:856
enable require.js:1176
enable require.js:1557
enable require.js:1161
bind require.js:134
each require.js:59
enable require.js:1113
init require.js:788
o require.js:1460
setTimeout handler*req.nextTick< require.js:1815
o require.js:1449
requirejs require.js:1797
<anonymous> wrapper.js:3
require.js:168:16
Loading failed for the <script> with source “https://forum.code-operative.co.uk/assets/src/modules/timeago/jquery.timeago.js?v=ohhorhrib2o”. login:1:1
Uncaught Error: Script error for "timeago/jquery.timeago"
https://requirejs.org/docs/errors.html#scripterror
makeError require.js:168
onScriptError require.js:1738
load require.js:1943
load require.js:1685
load require.js:834
fetch require.js:824
check require.js:856
enable require.js:1176
enable require.js:1557
enable require.js:1161
bind require.js:134
each require.js:59
enable require.js:1113
init require.js:788
o require.js:1460
setTimeout handler*req.nextTick< require.js:1815
o require.js:1449
requirejs require.js:1797
load app.js:97
<anonymous> app.js:23
jQuery 12
require.js:168:16
ServiceWorker registration failed: DOMException: The operation is insecure. app.js:793:13
There are also a slew of errors on restart, in the server-side log, which I can provide on request.
Our Cloudron platform is v v6.0.1. The NodeBB Cloudron package version is v1.17.0-1. (However, the version reported by NodeBB itself is v1.16.0. Should I expect these to be different?)
I find much help googling for any of the above errors - most cases the discussions seem to be several years old, and there is nothing I can see on this forum.
Are other people are not experiencing these problems? If not, it does seem like my installation may be damaged.
In which case, how can I safely rebuild it without losing the content? I suspect a Cloudron backup restore might restore the broken source code state as well as the content, and so I'm wary about trying that without some advice.
@yusf Oh. Doh. Thanks.
So I've worked around this by telling Firefox to "Forget this host" (right-click on an URL to get this option in the history tab), and thereby got to the web console that way.
However, it could still be handy to know how to trigger the renewal from the terminal, as this might not be the only case when you'd need to do it.
For whatever reason, my Cloudron server's dashboard no longer works. There is an error in the browser saying
Firefox detected a potential security threat and did not continue to <redacted co-op> because this web site requires a secure connection.
<redacted> has a security policy called HTTP Strict Transport Security (HSTS), which means that Firefox can only connect to it securely. You can’t add an exception to visit this site.
Under advanced it says:
<redacted> uses an invalid security certificate.
The certificate is not trusted because it is self-signed.
If I view the certificate, I see it is a wildcard cert with an expiry date in the distant future, so I suspect this is Cloudron's self-signed fallback certificate.
My first thought is to renew the certificate using Let's Encrypt. However, all the documentation I can find on this for Cloudron assumes you can access the web dashboard, which I can't.
Normally I would just do this on the terminal, but I don't know how to do this in a way which will accord with what Cloudron does normally. I can't see a timer job which runs a certbot script, for example.
So is there a way I can manually start the certbot renewal from the terminal?
And I would guess enabling HSTS makes the fall-back certificate unusable in any case?
Thanks
Scenario: forwarding email addresses from the Cloudron domain to 3rd party email services such as GMail
Problem: when SRS rewrites the email headers to allow the mail to be classified as legitimately from the forwarding Cloudron host, it can also cause the forwarded spam to appear to be sourced from that host, resulting in it being blacklisted.
Potential solution: implement adequate spam filtering for forwarded mail, for which no manual classification can be used to training a filter as could be for a local mailbox
Another possible solution in the case of GMail might be to implement POP3 and allow GMail to pull mail from that. GMail no longer supports arbitrary IMAP servers since releasing its newer "Gmailify" service.
See the original discussion here:
https://forum.cloudron.io/topic/3323/reading-a-cloudron-mailbox-using-gmail