Seeing as it is impossible for me to build or get an updated version of vanilla built, following @Linc 's advice I am migrating my site even though I love Vanilla.

I wish I didn't have to do it.

I leave you a small guide of what I did for anyone in my situation.

Migrating DB

I try 2 tools. With this I get convert the vanilla's data base to flarum. The conversion was poor.

You can export reactions manualy like likes or with the plugin reactions. If you need help to import likes, write me and I help you.

I think this is better tool, but I don't get it works: https://github.com/linc/nitro-porter

About flarum

It has an active community, plugins updated and a builded and updated release.

Its easy to install, only upload files and install.

https://docs.flarum.org/install/

If you use Rich2 on Vanilla

I prefere Rich2 text editor of vanilla, but you can use wysing with flarum.

With the tool I used, you can't convert posts.

You have to convert from json to html on vanillas database and then export.

I have wrote a script to do it. If you need it, I can share you It. Only write me.

A shame we have to leave Vanilla. I may be stupid, but I am not able to compile it.

our Zendesk can´t crawl through default Sitemap.xml file I believe because of it created a "Sitemap link" in the "Sitemap file". However Zendesk want to know the direct "Discussion" title to make it working for crawler. I can do this "new sitemap" by my own and host somehwere like AWS, but can I replace it on Vanilla Forum or not? And if I can does it accept the domain ownership verification when add back to Zendesk as it´s hosted on AWS?

Hope someone can help on this specific question.

Thanks in advance.

Tobias

When I inspect the page i see the following errors

Any ideas why this page will no longer load?

It produced this output:
Certbot failed to authenticate some domains (authenticator: apache). The Certificate Authority reported these problems:
Domain: mydomain.nl
Type: connection
Timeout during connect (likely firewall problem)

Hint: The Certificate Authority failed to verify the temporary Apache configuration changes made by Certbot. Ensure that the listed domains point to this Apache server and that it is accessible from the internet.

Some challenges have failed.
Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot wit h -v for more details.
myBB has been enabled at https://code2devops.com Please open this URL in a browser to complete the setup of your site.

Please help me resolve the issue

v.2.8

This was after a fresh install with version 2024.004.

I just tried downgrading to built-vanilla-2023.014 but that made no difference, still the same issue.

What can I try? Would appreciate your help!

However that all changed last weekend, when out of the blue the forum no longer works & when I try to go to it, or login to the admin end, I get:

"Something has gone wrong. We've run into a problem and are unable to handle this request right now. Please check back in a little while."

Since this is all I can get as an unhelpful error message, I have no idea what went wrong and in turn what I can do to fix it… or at a minimum extract an archive of the posts out.

Thanks!

We'd like to be able to let users know during signup about the forum rules, as well as provide some context for the various subforums.

I can't determine if this is possible in Vanilla?

Regards,

K

I'm encountering a critical issue on my self-hosted Vanilla Forum when trying to send private messages to users. The following fatal error is raised:

Fatal Error in Firebase\JWT\JWT.sign();

key must be a string when using hmac

Details:

• Environment:
  • Vanilla Forum version: 2024.007
  • PHP version: 8

Error Trace:

The error occurred on or near: /var/www/html/vendor/firebase/php-jwt/src/JWT.php

229:         list($function, $algorithm) = static::$supported_algs[$alg];

230:         switch ($function) {

231:             case 'hash_hmac':

232:                 if (!\is_string($key)) {

233:                     throw new InvalidArgumentException('key must be a string when using hmac');

234:                 }

235:                 return \hash_hmac($algorithm, $msg, $key, true);

236:             case 'openssl':

237:                 $signature = '';

Backtrace:

[/var/www/html/vendor/firebase/php-jwt/src/JWT.php:203] Firebase\JWT\JWT::sign();

[/var/www/html/applications/dashboard/models/class.activitymodel.php:1401] Firebase\JWT\JWT::encode();

[/var/www/html/applications/dashboard/models/class.activitymodel.php:1261] ActivityModel->getUnsubscribeLink();

[/var/www/html/applications/dashboard/models/class.activitymodel.php:2113] ActivityModel->email();

[/var/www/html/applications/dashboard/models/class.activitymodel.php:2510] ActivityModel->save();

[/var/www/html/applications/conversations/models/class.conversationsmodel.php:196] ActivityModel->saveQueue();

[/var/www/html/applications/conversations/models/class.conversationmodel.php:787] ConversationsModel->notifyUsers();

[/var/www/html/library/core/class.form.php:3122] ConversationModel->save();

[/var/www/html/applications/conversations/controllers/class.messagescontroller.php:116] Gdn_Form->save();

[/var/www/html/library/core/class.dispatcher.php:1036] MessagesController->add();

[/var/www/html/library/core/class.dispatcher.php:397] Gdn_Dispatcher->dispatchController();

[/var/www/html/index.php:36] Gdn_Dispatcher->dispatch();

It seems that the key being used for HMAC signing is not a string. I have traced the issue to line 232 in JWT.php, where the sign method expects the key to be a string.

Can anyone provide guidance on ensuring the key is always a string in the appropriate parts of the Vanilla Forum codebase? Is there a more permanent fix that can be applied to the source?

Thank you for your assistance!

Thanks!

I used to have the forum embedded in wordpress and was using the jsconnect sso solution to register and login users. Well, wordpress kinda went to hell and I unembedded the forum from wordpress and because the software is so old it uses recaptcha version one to do basic authentication. Well that isn't supported anymore so my forum is sort of dead in the water at the moment.

Wondering if there is anyway to upgrade from such an old version?

Tomorrow I am going to try to upgrade my site: https://success.vanillaforums.com/kb/articles/158-upgrading-self-hosted-vanilla

Thanks!

when i upload an image. this error will appear

How to fix it?

When you have lots of bookmarks and you list It, if you try to see the second or followings pages, it fails.

Is It a bug?

Thanks.

I think I'm closer to getting it.

When I get it I will publish each new version that they publish here in this forum. It's costing me my job.

I have this error when i try to do ./bin/release

Do you have any idea what could be wrong?

Thanks!

I have to admit i'm pretty new to Linux, but i never thought that a seemingly user-friendly distro like vanilla OS would drive me crazy and I'm at wit's end.

utilizing youtube and several AI's, the maze turned into a swamp pushing me deeper and deeper to a point where I succumbed and will turn to another distro. But not before first explaining what happened. I'm clearly frustrated, but i don't want to spread bad blood to his beautiful community nor being disrespectful to all the hard working developers. here is the straw that the broke the camel's back:

to prove that flatpak was properly installed:

linuxindeed@vanilla:~$ flatpak --version

Flatpak 1.14.0

1) installing flathub yielded an error:

linuxindeed@vanilla:~$ /etc/flatpak/flatpakrc.

bash: /etc/flatpak/flatpakrc.: No such file or directory

2) creation of the flatpackrx yielded next error:

linuxindeed@vanilla:~$ sudo touch /etc/flatpak/flatpakrc

touch: cannot touch '/etc/flatpak/flatpakrc': No such file or directory

3) granting permissions to directory:

linuxindeed@vanilla:~$ sudo chmod 755 /etc/flatpak

chmod: cannot access '/etc/flatpak': No such file or directory

4) manually creating the directory:

linuxindeed@vanilla:~$ sudo mkdir /etc/flatpak

linuxindeed@vanilla:~$ sudo chown -R flatpak:flatpak /etc/flatpak

chown: invalid user: ‘flatpak:flatpak’

5) creating the flatpak group:

linuxindeed@vanilla:~$ sudo groupadd flatpak

linuxindeed@vanilla:~$ sudo chmod -R g+rwx /etc/flatpak

linuxindeed@vanilla:~$ sudo chown -R flatpak:flatpak /etc/flatpak

chown: invalid user: ‘flatpak:flatpak’

6) reinitializing the group database:

linuxindeed@vanilla:~$ sudo rm -rf /etc/group.lock /etc/group

[sudo] password for linuxindeed: 

linuxindeed@vanilla:~$ sudo /usr/sbin/groupadd -r flatpak

linuxindeed is not in the sudoers file.

7) add the current user to the sudoers:

linuxindeed@vanilla:~$ sudo visudo

linuxindeed is not in the sudoers file

8) unlocking the file:

linuxindeed@vanilla:~$ sudo chmod +w /etc/sudoers

linuxindeed is not in the sudoers file.

9) creating new user with root privileges:

linuxindeed@vanilla:~$ sudo adduser newuser --root

linuxindeed is not in the sudoers file.

10) same error when trying the pkexec adduser command

when i was furhter suggested to rebuild the root user account, i yielded and thought, this is all just too much for someone who is trying to learn linux.

Anyways, I assume that I did sth wrong down the line, but I really don't have the time and fortitude to dive futher into this and hope that this might help the community for furture considerations.

Cheers and have a good day!