Как исправить ошибку «The feature you requested is currently unavailable. Please try again later» на ютуб при обновлении шапки канала
Капризничают не только дети и женщины, но также техника и сервисы в Интернете. Ломаются ноутбуки, стиральные машины, замки в дверях и даже прорывает трубу отопления среди ночи. С начала этого года я испытала все эти радости буквально один за другим.
Например, сейчас у меня возникла проблема с очень небезызвестным сервисом (не буду произносить вслух, как “его”зовут), со счета которого вот уже второй месяц я не могу вывести деньги. Целый месяц служба поддержки меня “кормила завтраками”, и вроде бы только сейчас получилось выйти на конструктивный диалог. Хотя бы я наконец-то услышала слова, что нам это тоже очень не нравится, и мы делаем попытки решить эту проблему. Пишу, и самой смешно). Если задать мне вопрос, почему так происходит? Я знаю на него ответ, но только это тема другого блога.
При каждой попытке обновить шапку ютуб, появлялось окно сначала с необходимостью авторизации в google аккаунте, и это требовалось сделать два раза. А потом на полэкрана разворачивалось сообщение «The feature you requested is currently unavailable. Please try again later». Суть ошибки якобы заключалась в том, что сейчас эта функция не доступна, и необходимо повторить действие позже. Не стоит себя обнадеживать и ждать это “позже”: и через час, и даже на следующий день ошибка эта никуда не исчезнет.
А где же решение?
Оказалось, что проблему можно было решить буквально за 1 минуту. Ведь все дело в ваших настройках браузера. В браузере есть “вредная” галочка, которую нужно отключить. И не важно, о каком браузере идет речь: Opera, Google, Яндекс…
Я покажу на примере Яндекса, потому что чаще всего работаю в нем. Привыкла к “родненькому” и еще к Алисе, которая постоянно выскакивает, даже, если я зову свою кошку: “Ириска-Ириска, иди сюда!”
Перейдите в настройки браузера — Сайты — Расширенные настройки сайтов — раздел Cookie-файлы.
Чтобы при обновлении шапки канала на ютуб исчезла ошибка «The feature you requested is currently unavailable. Please try again later» просто необходимо снять галочку около опции Блокировать данные и файлы сторонних сайтов. И все!
Теперь возвращайтесь на ютуб и попробуйте загрузить изображение снова. Все получится, я обещаю).
Автор статьи Ольга Абрамова, блог Денежные ручейки
Powershell error saying the gallery is unavailable try again later
I am running into this issue where iam unable to install any modules. even when i try to register i get this error. any ideas on resolving this appreciate it.
— adding some more commands
Register seems to complete without any errors, but nothing gets added
3 Answers 3
Try forcing tls 1.2. This solves most powershell gallery issues
Not really a solution, but rather an FYI piece. This also seems to happen regularly every three months now when TLS cert in https://www.powershellgallery.com/api/v2 expires. For some reason, Microsoft are struggling to get the cert renewal to work properly.
When this happens, none of the above mentioned solutions will work. In fact, this is happening right now, as I type this. https://github.com/PowerShell/PowerShellGallery/issues/166
To see if the issue is caused by the expired (or otherwise invalid) cert, just open this URL https://www.powershellgallery.com/api/v2 in a browser and see if the browser complains about the certificate.
If you need to make it work just this one time, you can try tricking Powershell into ignoring invalid certificates like so:
a) this is a bad practice and you shouldn’t really have it as a permanent solution because this will expose you to man-in-the-middle attack; and
b) this may not help you because Microsoft guys usually disable PSGallery API when this situation happens. To check if the API is disabled right now, run:
Another power action is being processed: bug in runc causing container lockup #2475
Comments
INfoUpgraders commented Oct 10, 2020 •
⚠️ NEW READERS! PLEASE READ ENTIRE THREAD. ⚠️
Most of the context and a good starting point can be found in these specific comments. Please only respond if including more relevant information, or confirmation of bug fixes.
Panel or Daemon: Panel
Error Event [3872f642-7497-4b62-b9c2-5116d28836d3]: another power action is currently being processed for this server, please try again later
Over 750+ servers are running on this node consisting of Minecraft and Discord bots
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Not expecting for when multiple servers try to start at the same time for it to error out 🙂
The text was updated successfully, but these errors were encountered:
matthewpi commented Oct 10, 2020
The power action limit is handled on a per-server basis, it’s not for all the servers entirely.
DaneEveritt commented Oct 10, 2020
As @matthewpi said, additionally you can always kill a server if it is for some reason stuck in a power state which will get it back into working order.
INfoUpgraders commented Oct 10, 2020
Well this only happens when multiple people are trying to do a power action on their server. Killing a server simply results in the same issue, if you’d like, you can add me on Discord @ INfoUpgraders#1 and we can further the topic and I can show you guys what is happening exactly.
DaneEveritt commented Oct 10, 2020 •
You’re welcome to use the #1.0-rc-help channel on Discord to discuss this, however with the limited information provided here I’m not sure how we can really debug this any more and I’ve not heard from anyone else encountering this issue.
INfoUpgraders commented Oct 11, 2020 •
This is what happens, usually waiting a while and trying again solves the issues. But I feel as this is a bug with multiple people possibly trying to do things at once. If you need anything else, just let me know in the help channel as I posted the same gif there.
Malachiel87 commented Oct 12, 2020
I confirm the issue, same thing happened to me, if i shutdown the server and go back to console and try to turn on i face the same error ^
INfoUpgraders commented Oct 13, 2020
@xion87 Roughly, how many servers and members do you have on your panel?
AaduMaadu commented Feb 1, 2021 •
Same, this bug has made it impossible to start my servers anymore
This comment was marked as spam.
matthewpi commented Feb 1, 2021
Yeah, and the devs made it completely intentional.
This is a feature designed to prevent race conditions and triggering multiple power actions at the same time (whether it is done by multiple users or an individual). Sadly with the way software works and the complexity of systems like this, it isn’t simple to find out if there is actually a problem or if it is behaving as intended. Also, with the amount of people that actually use Pterodactyl for both hosts and personal use, this only seems to affect a very small part of users, which leads me to believe it isn’t a problem.
This comment was marked as spam.
This comment was marked as spam.
This comment was marked as spam.
This comment was marked as spam.
This comment was marked as spam.
This comment was marked as spam.
Justinborzi commented Feb 2, 2021
I can say it happened to me before, and from some debugging, I think I slightly concluded it’s from having too many servers on one machine. On saying that, It was a fairly low server count compared to 0.7x series, but I do agree with you Matthewpi, I’d say it is behaving intentionally with a bug being the handling of x number of requests. I would love to see it fixed nonetheless if possible.
This is a feature designed to prevent race conditions and triggering multiple power actions at the same time (whether it is done by multiple users or an individual). Sadly with the way software works and the complexity of systems like this, it isn’t simple to find out if there is actually a problem or if it is behaving as intended. Also, with the amount of people that actually use Pterodactyl for both hosts and personal use, this only seems to affect a very small part of users, which leads me to believe it isn’t a problem.
DaneEveritt commented Feb 2, 2021 •
Unless you’re going to respond with enough information for us to even begin trying to reproduce, please stop commenting with «this happens to me too.»
It’s been four months since this was reported, please include the relevant version information, steps you took that lead to the issue, and what specific eggs your server(s) are running that are encountering this issue. If you cannot or will not provide that, please don’t rely to this issue, thanks!
We have limited time and resources for debugging things as it is, and bug reports like this don’t take high priority since the only steps we’ve been given are to run 750 Minecraft and discord servers and then press a start button. Additionally, thousands of people run this software and I’ve not heard from others indicating this is an issue for them. I get that it being broken for you can be frustrating, but you’re not the only users of this software, and it helps if you look at this issue with a fresh pair of eyes to understand how frustrating your responses are to us without any additional context to them. 👌🏼
INfoUpgraders commented Feb 2, 2021 •
Hello Dane, I understand your frustration as I know there are limited developers and contributors to such a large project. I apologize for not providing correct and enough information in my initial thread.
Version Information: All minor versions of 1.x.x panel w/ corresponding wings.
Steps to reproduce:
I understand this may not be optimal for a test/dev environment, but this is what it takes to reproduce the «bug».
Eggs that are encountering this issue: Default eggs that come with the panel, as well as custom eggs.
I appreciate your response and hope this is enough information for you, please let me know if you need anymore!
DaneEveritt commented Feb 2, 2021
@INfoUpgraders I need you to provide the entire output of the wings diagnostics command, it has a ton of contextual information that we need in order to even begin trying to debug this. I literally do not have the resources (or time) available to spin up 100+ server instances just to try and hunt down this type of bug.
AssaultLine commented May 21, 2021
The original poster said that a requirement of hundreds of containers was needed. I have less than 10 and have it happening. I am currently running on Ubuntu 20.04 on the node that is giving me trouble currently and there is only 6 containers installed on it via pterodactyl.
I am running the newest version of Panel and Wings, and I am only having this issue mainly with a few specific nodes. They all were installed and set up the same though.
You have no clue how much trouble it is trying to get this fixed, I have people constantly contacting me about their server getting stuck in the same cycle and there is nothing I can do to fix it for them other than restart every node on that dedi.
Specs:
Ryzen 9 3900
128GB RAM
2TB NVMe
Only 6 servers currently installed and its getting the bug at random
Newest version of panel and wings like I already mentioned
Let me know what else is needed and I will try to provide.
AssaultLine commented May 21, 2021
Also to add onto that a bit more, I have found that a power action from a customer/user is not even necessary. At times the server was left running overnight and when the person using the server hops on in the morning it will be off, or at least shown as off in the servers dashboard page. Any power action will give the same error with different Error Event code.
Error Event [e9848364-f97d-4e5c-bd28-1e0da8c6b24c]: another power action is currently being processed for this server, please try again later
KoddyDev commented May 21, 2021
how to solve without restart my docker and my online servers?
DaneEveritt commented May 21, 2021
You just need to restart wings, you don’t have to restart docker.
AssaultLine commented May 21, 2021
I’m going to test this again, but the last time I restarted wings while the server was in this state it then disconnected my entire node and I was forced to restart all of docker anyways to get wings connected back.
AssaultLine commented May 21, 2021
Already tested it and its just like I said, if there are any servers that are in this state where the show that error, and I restart wings then that whole node now shows as offline. And the only way to resolve the node not connecting back is to systemctl restart docker. I believe this has something to do with docker and wings not properly communicating the state of the server and then it won’t connect back until it detects the server in the proper state that it should of been in. This is all just my opinion, but this has something to do with docker or wings.
Is there some way for me to disable this specific security setting that causes that error to show in the first place? I’m just wondering what happens if whatever is set to trigger that error is all of a sudden disabled.
AssaultLine commented May 21, 2021
Or possibly could you tell me what file it would be in that tells wings what state the server is in? Maybe I am able to manually edit the file to fix it rather than restarting all of docker.
I just hate when it happens and the only way to resolve is to kill literally every server hosted on that node. Its upsetting other people and I have so few people per node to begin with. All my dedi’s are 12 core or less and I only host up to 12 servers on a node.
DaneEveritt commented May 21, 2021 •
This logic is controlled by a little internal code lock, theres no reason I can think of that restarting wings wouldn’t correctly clear that lock.
AssaultLine commented May 23, 2021
Something I noticed though is it outputs there is 6 containers but in reality there is only 5 servers installed on that server. And its a fresh install also. Once I restarted docker it went from 4 containers running to 5 containers running and 1 stopped. Is there any useful diagnostic info that I can provide you guys to help more?
AssaultLine commented May 23, 2021
I had the same thing happen on another new node that was just installed. I did the command on here and it showed something a bit different. It shows that the server was exited about 5 hours prior and that it had an error 137 (not sure what that error defines)
This server was suffering from the same issue as the other one though.
INfoUpgraders commented May 24, 2021 •
How much ram did that Morhau game server have? That container crashed because it ran out of memory, you also can enable OOM killer in that containers settings
AssaultLine commented May 24, 2021 •
How much ram did that Morhau game server have? That container crashed because it ran out of memory, you also can enable OOM killer in that containers settings
It should have enough where its not going to crash from that. I am currently dealing with the whole node not connecting back though after restarting docker to fix a server. This happens a lot now and I have no solid way of fixing it once it gets to this stage. I am checking wings debug and seeing this
All of the GET errors near the end are the 2 webpages that I have opened trying to get the server dashboard to load and its throwing out those debugs on it.
DaneEveritt commented May 24, 2021
Sorry, can you try docker inspect on a container having issues for me?
AssaultLine commented May 24, 2021
I tried this and it wouldn’t even output anything from that container, but when I tried it on a container not currently bugged it showed a lot of details and info. Most of the time I can’t get docker to do anything regarding the bugged container, I am just forced to restart it to fix the problem.
DaneEveritt commented May 24, 2021 •
This sounds like it is related to another issue where Docker completely locks up for random containers.
edit: Couldn’t find the specific issue from here, but I remember debugging it on a hosts’ instance and it was exactly the same issue where random containers would completely lock up.
cc @matthewpi do you remember anything about this?
App gallery не возможно купить
Не работает Донат wot blitz ошибка
Your login has failed, please try again later.
Прикрепленные файлы
Так пиши в цпп блица. Причём тут форум.
Если что писал в тех поддержку 3 раза
Если у тебя не Huawei, то там нужно еще HMS Core ставить.
Если не поможет, то считай, что твои кровные сберегли всевышние силы.
Если у тебя не Huawei, то там нужно еще HMS Core ставить.
Если не поможет, то считай, что твои кровные сберегли всевышние силы.
ОН У МЕНЯ ЕСТЬ посмотри дальше в других играх все нормально вылазит
Drupal. Что делать с ошибкой «The website encountered an unexpected error. Please try again later.»
Такой вид ошибки может появиться во время установки демо профиля. Она означает, что не все таблицы были перенесены во время установки демо профиля. Для того чтобы избавиться от этой ошибки нужно сделать следующее:
1. Откройте базу данных Drupal. Удалите все таблицы, если они доступны.
3.Перейдите во вкладку Import (Импорт) и перенесите sql файл в Вашу базу данных.
4. Обновите сайт. Сейчас сайт должен быть доступен.
Иногда после этого может появиться пустая страница. В этом случае обратитесь к хостинг провайдеру и попросите увеличить значение «memory_limit» опции PHP.
Пожалуйста, ознакомьтесь с детальным, обучающим видео ниже:
