The user Taste-OF-IT encountered a duplicate wasm extension error in Nginx after attempting to switch from the beta branch to stable in their Discourse installation. pfaffman clarified that switching to stable is only possible after a new stable release, not before. Canapin questioned the user’s use of dev instead of beta, and Moin referenced a guide stating that switching to stable should occur after the release of 3.4.0. Taste-OF-IT later confirmed that their setup is functioning normally with the beta3 version and that the behavior aligns with expected Discourse release patterns.
Hi Jay,
ok i switch back and rerun rebuild and discourse worked again. I read in the forum and it seems that i understand the explanation wrong. So thanks now its clear.
Hi Jay,
i now switch back, have successfull updated to latest dev Version, reconfigure to stable and run rebuild and now i got the same error message. Any Idea?
Thx
Out of curiosity, why do you want to use the stable branch?
As I’m understanding Jay, the beta branch will always be more recent than stable, and you can’t go back to an older version of Discourse. Which may (or not) be the underlying cause of the error you have
On another test installation, the Installation of Discourse is with no Version configured. The UI shows Version 3.4.0.beta3-dev is running, the Updater shows now 3.4.0.beta3, which i understand is the stable version. I find this Is Discourse always in "beta"? - #23 by kwinz and i now understand that this is the normal behavior with dev and beta3. So if you have no other information, i am fine with this.