Unable to post to the forum
![[Deleted User]](https://we.vanillicon.com/v2/e9cf9aa5f47d15209857de0392febb34.svg)
trying to post useful information about the repos, but get ----------------- SORRY, YOU’VE BEEN BLOCKED You are unable to access the Vanilla Network. Why have I been blocked? This website is using a security service to protect itself from online attacks. The action you just performed triggered the security solution. There are several actions that could trigger this block including submitting a certain word or phrase, a SQL command or malformed data. What can I do to resolve this? You can email the site owner to let them know you were blocked. Please include what you were doing when this page came up and the Cloudflare Ray ID found at the bottom of this page. Your IP: XXXXXX Ray ID: XXXXXX Help Performance & Security by Vanilla Forums Inc. -----------------
1Password Version: Not Provided
Extension Version: Not Provided
OS Version: Not Provided
Browser: Not Provided
Comments
-
Hello @pgnd! 👋
I'm sorry that you're unable to post information onto the forum. Please send the content of your post to
support+forum@1Password.comso that the team and I can look into this further. Include a link to this thread with your email.After emailing in, you'll receive a reply from BitBot, our friendly robot assistant with a Support ID that looks something like [#ABC-12345-678]. Post that here, and I'll be able to locate your message and take a look.
-Dave
0 -
I've sent full details to support already. All I got back is "our developers will look into it" and "please send diagnostic logs".
Both completely ignoring the problem -- which is your out of date repo.
After three weeks of incaction, this seemed like the next best option. Instead, just the reco to repeat email to support.
0 -
It'd be useful if you didn't change the title of my post.
0 -
Occasionally we may change titles to make the post more obvious and descriptive. That said, I'm not aware of it being changed. It's possible it was changed by one of the other staff. It is likely your post was moved within the community. Especially, if it was posted in another category by mistake.
Do you have a support ID you can share with me? I'm one of the admins here in the community. I'd like to locate your message and look into it. I did not find a report/email using the email address you used here in the community.
0 -
date Sat Jul 27 09:31:08 AM EDT 2024 1pass beta changelog July 25 2024 1Password for Linux 8.10.38-29 July 17 2024 1Password for Linux 8.10.38-13 July 10 2024 1Password for Linux 8.10.38-10 |-> July 2 2024 | 1Password for Linux 8.10.36-35 | | dnf clean all | dnf update | dnf repoquery 1password\* --repo=1password | | DNSSEC extension: Testing already imported keys for their validity. | Last metadata expiration check: 0:22:57 ago on Sat 27 Jul 2024 09:05:24 AM EDT. |-> 1password-0:8.10.36~35.BETA-1.x86_64 1password-cli-0:2.30.0-beta.02.x86_640 -
Thanks @pgnd
My apologies. I had thought that you posted the inability to post to the community as a support request and that's where you needed further support. I thought someone had asked you for a report in error and I wanted to look into it for you. I should have made my post clearer. No wonder you asked about your post title. I too would have went huh. As an admin I can also see why it might have been renamed when looking at your first post in this topic.
I was unaware you had sent an actual support request for a product. If you sent that to my colleagues in email support, they would be the best ones to help. Please continue the conversation with them if needed.
0 -
If you sent that to my colleagues in email support, they would be the best ones to help. Please continue the conversation with them if needed.
they've done nothing in three weeks of "continued conversation". hence the (failed) attempt to get attention/resolution here 'in community'.
let's forget it. it's not worth the time trying to provide useful feedback @ 1pass betas.
0 -
It possible the team has a known issue filed and they are working with it. Bugs in the beta may not necessarily be resolved until a fix is determined and it has been tested in the nightly.
0
