Если Вам понравилась атмосфера форума, заходите к нам чаще! С уважением, source777.

[ Время генерации скрипта: 0.1249 ] [ Использовано запросов: 21 ] [ GZIP включён ]

We’re sorry, but something went wrong heroku rails

I am having problems deploying a rails 3.2 app with heroku, I am getting the above error when I load the app. Here are my logs:

I am fairly new to rails/heroku, so any help is much appreciated. I am trying to deploy after alot of development. For the future, is it better to push to heroku early in the development process and then keep pushing as you go? Thanks!

1 Answer 1

ActiveRecord::StatementInvalid (PG::Error: ERROR: relation «houses» does not exist.

For the future, is it better to push to heroku early in the development process and then keep pushing as you go?

At the project I am currently working with our team, we have 2 instances of heroku, means 2 apps, one is for production, the second for testing, changes are pushed to testing app first and if all goes well we move it to production.

Edit

As I found out your are using sqlite for development:

Remove sqlite3 or move it into a development group in your Gemfile like this:

or easier, just use PG on your local computer for development. You might have some sql statements that will work in sqlite and will not work in postgres on heroku, so in your place I would use PG on development.

We’re sorry but work doesn’t work properly without JavaScript enabled. #5470

Comments

alien-neko commented May 12, 2020

Version

Environment info

Steps to reproduce

I created a VueJS app and I’m getting the following error when I look at the source code in the web browse

We’re sorry but work doesn’t work properly without JavaScript enabled. Please enable it to continue.

What is expected?

Vue running smoothly

What is actually happening?

The text was updated successfully, but these errors were encountered:

sodatea commented May 12, 2020

It’s expected. The Preview panel will try to render HTML but it does not run JavaScript so it only shows the content of the tag.

The full source code is shown in the Response tab.

babak-karimi-asl commented Aug 1, 2020

elizavetaanisimova commented Aug 2, 2020

I have the same problem, Xcode
Asks to enable javascript, how can I enable it?

babak-karimi-asl commented Aug 5, 2020 •

my problem solved by replacing vue instantiation code in main.js with the following :

one of my colleagues did this i don’t know from where.

kennyj2016 commented Sep 16, 2020

I had mine resolved. It was due to a CORS policy setting. You may want to check your server’s CORS policy setting. For Django, it needs following to be set in the settings.py if CORs module is installed.
CORS_ALLOW_ALL_ORIGINS = True

Other servers may have different syntax or configurations.

We’re sorry, but something went wrong #341

Comments

bzbzh commented Aug 22, 2018 •

We’re sorry, but something went wrong.

We’ve been notified about this issue and we’ll take a look at it shortly.

And yet log-in directly from portal clicking on the company app is working.

The URL giving this error looks like:
[xxx].onelogin.com/trust/saml2/http-post/sso/8[. ]1?SAMLRequest=lVNNj9[. ]3D&RelayState=htt[. ]dex.php

The text was updated successfully, but these errors were encountered:

pitbulk commented Aug 22, 2018

That error message came from OneLogin and not from the php-saml toolkit.

Can you verify that the user you are trying to log in has access to the App (Check it on the SAML connector at OneLogin)?

bzbzh commented Aug 23, 2018

It has since I can log to the app directly from OneLogin website (clicking the app logo).

pitbulk commented Aug 23, 2018

Then you will need to create a support ticket at OneLogin since the error came from the OneLogin platform.

This github space is to solve code issues, not for offer this kind of support.

We’re sorry, but something went wrong. (Rails, Nginx, Puma, Postgres, Capistrano)

So I have been trying to deploy my rails app with no luck. There is no problem when I run:

but when I open my server ip, the only thing I see is:

We’re sorry, but something went wrong.

If you are the application owner check the logs for more information.

And I have checked the production.log the output is:

How do I fix this? What could be the problem, any ideas?

Know someone who can answer? Share a link to this question via email, Twitter, or Facebook.

Browse other questions tagged ruby-on-rails ruby ruby-on-rails-3 postgresql nginx or ask your own question.

Related

Hot Network Questions

Subscribe to RSS

To subscribe to this RSS feed, copy and paste this URL into your RSS reader.

By clicking “Accept all cookies”, you agree Stack Exchange can store cookies on your device and disclose information in accordance with our Cookie Policy.

We re sorry but something went wrong

The big problem is that it is wrong since more than 2 months. And i have to use back IE only for fb.

Occurency : always Firefox version : up to date, now v15 Extension and plugins : default ones Conditions : brand new PC at work

For info, i have the same issue on my home PC since 3 months, since FF12 release, in this case with plugins protecting privacy. But even desactivated, it is not working. As a first contact, i posted related bug report in fb process, but i never had any reply since, neither one email to confirm bug report.

How to do, please?

Modified September 5, 2012 at 3:50:19 PM PDT by kokoro

Chosen solution

This can be caused by blocking cookies from specific domains.

Do you have the cookie settings set to «Ask me every time»?

You can remove a possible cookie exception for www.facebook.com and create an exception for facebook.com instead to include all facebook domains.

All Replies (4)

Clear the cache and the cookies from sites that cause problems.

«Clear the Cache»:

«Remove Cookies» from sites causing problems:

Start Firefox in Safe Mode to check if one of the extensions or if hardware acceleration is causing the problem (switch to the DEFAULT theme: Firefox/Tools > Add-ons > Appearance/Themes).

This office PC is brand new, and same behavior as at home. Here, i have default theme and no plugin/extension installed since PC delivery.

I cleared the cache&cookies (as i did many times trying to solve by myself this issue). And in safe mode, i have the same issue :

Chosen Solution

This can be caused by blocking cookies from specific domains.

Do you have the cookie settings set to «Ask me every time»?

Heroku error: We’re sorry, but something went wrong

i have deployed an app to heroku(finance tracker under «ROR developer course» from udemy.com). The login button works fine but when i click on the signup button, it gives me this error

I have ran heroku run rake db:migrate successfully. I used devise gem for authentication. Pls any idea someone. thanks

2 Answers 2

Trending sort

Trending sort is based off of the default sorting method — by highest score — but it boosts votes that have happened recently, helping to surface more up-to-date answers.

It falls back to sorting by highest score if no posts are trending.

Switch to Trending sort

So the first thing you should do is go to the Heroku admin panel for your app and look through the log file. You should find a stack trace (should look like an error followed by a bunch of method calls and line numbers). Another option is for you to remotely access the app server, go to you Heroku app directory on your computer and run (assuming you have Heroku CLI installed)

then navigate to your log directory and run

(log file should be production.log or develop.log) and that will show you a real time stream of the log activity, so just go recreate the bug and see what happens.

Replace these lines

With these lines

What happened is the gem devise that you are using changed its API in version for so the syntax you are were using is no longer valid. I am assuming that at some point in time you did a bundle update or something that inadvertently upgraded you gem

sonarqube updatecenter error We’re sorry, but something went wrong

I can see the following error in sonar.log:

8: 9: @rescues_path[«rescues/_trace.erb»] %> 10: gems/gems/actionpack-2.3.15/lib/action_controller/templates/rescues/diagnostics.erb:7 org/jruby/RubyKernel.java:2227:in `send’ gems/gems/actionpack-2.3.15/lib/action_view/renderable.rb:34:in `render’ gems/gems/actionpack-2.3.15/lib/action_view/base.rb:306:in `with_template’ gems/gems/actionpack-2.3.15/lib/action_view/renderable.rb:30:in `render’ gems/gems/actionpack-2.3.15/lib/action_view/template.rb:205:in `render_template’ gems/gems/actionpack-2.3.15/lib/action_view/base.rb:265:in `render’ gems/gems/actionpack-2.3.15/lib/action_controller/rescue.rb:133:in `rescue_action_locally’ gems/gems/actionpack-2.3.15/lib/action_controller/rescue.rb:152:in `rescue_action_without_handler’ gems/gems/actionpack-2.3.15/lib/action_controller/rescue.rb:73:in `rescue_action’ gems/gems/actionpack-2.3.15/lib/action_controller/rescue.rb:162:in `perform_action_with_rescue’ gems/gems/actionpack-2.3.15/lib/action_controller/rescue.rb:160:in `perform_action_with_rescue’ gems/gems/actionpack-2.3.15/lib/action_controller/flash.rb:151:in `perform_action_with_flash’ org/jruby/RubyKernel.java:2235:in `send’ gems/gems/actionpack-2.3.15/lib/action_controller/base.rb:532:in `process’ gems/gems/actionpack-2.3.15/lib/action_controller/filters.rb:606:in `process_with_filters’ gems/gems/actionpack-2.3.15/lib/action_controller/base.rb:391:in `process’ gems/gems/actionpack-2.3.15/lib/action_controller/base.rb:386:in `call’ gems/gems/actionpack-2.3.15/lib/action_controller/routing/route_set.rb:450:in `call’ gems/gems/actionpack-2.3.15/lib/action_controller/dispatcher.rb:87:in `dispatch’ gems/gems/actionpack-2.3.15/lib/action_controller/dispatcher.rb:85:in `dispatch’ gems/gems/actionpack-2.3.15/lib/action_controller/dispatcher.rb:121:in `_call’ gems/gems/actionpack-2.3.15/lib/action_controller/dispatcher.rb:130:in `build_middleware_stack’ org/jruby/RubyProc.java:290:in `call’ org/jruby/RubyProc.java:224:in `call’ gems/gems/activerecord-2.3.15/lib/active_record/query_cache.rb:29:in `call’ gems/gems/activerecord-2.3.15/lib/active_record/connection_adapters/abstract/query_cache.rb:34:in `cache’ gems/gems/activerecord-2.3.15/lib/active_record/query_cache.rb:9:in `cache’ gems/gems/activerecord-2.3.15/lib/active_record/query_cache.rb:28:in `call’ gems/gems/activerecord-2.3.15/lib/active_record/connection_adapters/abstract/connection_pool.rb:361:in `call’ gems/gems/actionpack-2.3.15/lib/action_controller/string_coercion.rb:25:in `call’ gems/gems/actionpack-2.3.15/lib/action_controller/params_parser.rb:15:in `call’ file:/F:/Program Files/sonarqube-5.0/sonarqube-5.0/lib/server/jruby-rack-1.1.13.2.jar!/jruby/rack/session_store.rb:70:in `context’ gems/gems/actionpack-2.3.15/lib/action_controller/failsafe.rb:26:in `call’ gems/gems/actionpack-2.3.15/lib/action_controller/dispatcher.rb:106:in `call’ file:/F:/Program Files/sonarqube-5.0/sonarqube-5.0/lib/server/jruby-rack-1.1.13.2.jar!/rack/adapter/rails.rb:34:in `serve_rails’ file:/F:/Program Files/sonarqube-5.0/sonarqube-5.0/lib/server/jruby-rack-1.1.13.2.jar!/rack/adapter/rails.rb:39:in `call’ file:/F:/Program Files/sonarqube-5.0/sonarqube-5.0/lib/server/jruby-rack-1.1.13.2.jar!/rack/handler/servlet.rb:22:in `call’

Im using the Sonaqube 5.0, java 8 and mysql 5.6 server. It is working very well for past 1 year. Today I tired to check for updates and i got this error. Please help me on this. Thanks.

Heroku «We’re sorry, but something went wrong» after Postgres migration

I recently did Heroku’s requested database migration from a «shared database» to Postgres. I followed Heroku’s directions carefully, and it all went fine until the last step: removing the old shared database. At that point, my app went down with the «something went wrong» message, and it’s been down ever since (going on two weeks now).

Note that the app was still working after the step in which I switched to the new database, and according to «heroku config», it is using the new database. It shouldn’t care about the old one disappearing. The logs say nothing other than 500 errors.

I submitted an urgent support request to Heroku, but they were not helpful. They just said that my data is still there but, «Your application isn’t logging so it’s not clear why this is happening but it doesn’t appear to be due to the migration.» That was a week ago, so it’s not looking like they’re going to do anything more.

I agree that the problem shouldn’t be due to the migration, but given that I’ve made no changes to the app except the migration, and that it died exactly when I removed the old database, I don’t see what else it could be.

My app is probably pretty old at this point (Rails 3.0.3), so my only thought now is to update everything to the latest versions and redeploy. The app is used to record merit badges and rank advancements for our local Boy Scout troop, so I really need to get it running again. Any advice would be greatly appreciated.

Network Monitor «We’re sorry, but something went wrong»

We are having an issue with our Network monitor. Has been working fine up till this point in time. We are running Version 1.5.111 on a 64bit Window 10 Professional tower. Our Spiceworks is located on a different Server.

Hi guys, talked with our Ops team. This is a continuation of some issues we’ve had recently with our load balancer. We think it was affecting the Community as well, but in a less noticeable way. Both cases seem to have been inconsistent (did not affect 100% of connections).

Packet inspection revealed a problem with cipher negotiation that was causing a failure connecting between your client (your Network Monitor app) and the accounts service and Community. This explains why auth was failing and emails were also held up.

The fix involved creating a new cipher configuration on our load balancer that controls which TLS ciphers are available for negotiation on client and server. We didn’t recently change the configuration around these ciphers so we’ll be continuing to work with the load balancer vendor to understand why the existing cipher configuration unexpectedly stopped accepting some connections.

Sorry about the problems today. We have this thoroughly documented in case there are further issues with the load balancer that prevent connections, like this.

EDIT: Updated the technical bit in the 3rd paragraph to add some more details.

We’re sorry, but something went wrong Heroku

Don’t start app at Heroku. Migrate I was do, but it don`t work anyway. Please help my anyone

1 Answer 1

This error comes from your app’s code. However, your app is sending it’s logs to the local filesystem, which means you don’t see the exception in heroku logs.

You would need to configure your app to send logs to STDOUT or STDERR to be able to see them.
You can add the rails_12factor gem to your app, which will change your configuration to do just that.

Once you have added this gem to your app and redeployed it, the raised exception should show in your logs and you can fix in your app’s code.

Not the answer you’re looking for? Browse other questions tagged heroku or ask your own question.

Related

Hot Network Questions

Subscribe to RSS

To subscribe to this RSS feed, copy and paste this URL into your RSS reader.

By clicking “Accept all cookies”, you agree Stack Exchange can store cookies on your device and disclose information in accordance with our Cookie Policy.

FIX: We’re sorry, but something went wrong Instagram error

Instagram is one of the most popular social media platforms, that also allows you to use two accounts. And what is even more impressive is that Instagram Live is available to both Windows 10 PC and mobile users.

However, sometimes, the app might not work properly, as you won’t be able to run it in normal conditions.

Users described ending up with a crashed program or not being allowed to load any posts. Moreover, from what we found, issues can also appear when sending DMs to friends.

When attempting to connect you’ll get a message from Instagram, which says the following:

We’re sorry, but something went wrong. Please try again.

This may cause the platform to crash or just stop you from posting on Instagram, and we truly understand how irritating it can be.

We selected only the best options to quickly solve this annoying issue. Make sure you keep reading our guide to find them all. But first, let’s see some common reasons why the error shows up in the first place.

Why does the Instagram error: Sorry, something went wrong appear?

There are two main leading causes for Instagram bugs: the service is down or there is a problem with your Internet connection.

Before assuming that Instagram got glitches, you should first check whether the app is down all over the world or not. Yes, note that sometimes it faces issues globally, and other times it only affects specific regions.

However, account glitches are the most common reasons that explain why the Instagram error: We’re sorry, but something went wrong appears.

Quick Tip:

Try opening the platform using Opera. It has built-in integrations for Instagram, both for computer apps and mobile. Enter your credentials and access the feed from the sidebar.

Opera is a secure browser, with anti-tracking features, plus a free, unlimited VPN to make sure all your private data stays protected.

Opera

Remove errors and keep track of your Instagram feed, and quickly respond to your messages directly from the sidebar!

How can I fix the Sorry, something went wrong error?

1. Make sure that Instagram server is available

Sometimes, Instagram servers can be temporarily unavailable. You can confirm this by using a live outage map online or ask your friends if they are having the same issue.

Just confirm that the problem is only related to your account and not to the entire Instagram server.

2. Login through Facebook

Note that this can only be possible if you had earlier connected these two accounts. So, it is advisable to get your Facebook and Instagram accounts connected.

Expert Tip: Some PC issues are hard to tackle, especially when it comes to corrupted repositories or missing Windows files. If you are having troubles fixing an error, your system may be partially broken. We recommend installing Restoro, a tool that will scan your machine and identify what the fault is.
Click here to download and start repairing.

Linking them can prevent from being hacked and help quickly resolve the Sorry something went wrong Instagram error.

Since the day Facebook bought Instagram, the connection between the two of them has become extremely significant. There even are some features, like Instagram ads, that you can enjoy through Facebook.

If these options didn’t work for your situation, make sure you check and try the other listed ones.

3. Use the Windows 10 Instagram app

In case the Instagram app is not working on your computer, take a look at some useful tips to solve the issue right away. Up next, you are clearly ready to contact your friends, so check out how to send direct messages from PC.

4. Temporarily disable your account

The We’re sorry, but something went wrong Instagram error might occur randomly, so temporarily disabling your account can clear the app from any glitches.

In case you choose to use this option, your photos, comments, and likes will be hidden until reactivating your profile. Also, note that you can only disable the Instagram account from a computer or mobile browser.

5. Uninstall and reinstall the Instagram app

You can quickly uninstall and reinstall your Instagram app yet keep in mind that this solution works only if you’re using the Windows 10 Instagram app.

Uninstalling the app on your phone or computer will only delete it. All your content, like photos, tags, likes, or comments will still be there.

When you reinstall Instagram, sign back in as uninstalling it will log you out. The process doesn’t do anything to your profile and everything will be the same when you start using the app again.

6. Contact Instagram Help Center

Check out some others Instagram problems

The Something went wrong error was just one example, but you might encounter some other annoying Instagram issues. Take a look at the following list including the most common ones:

Is Instagram one of the most popular social platforms?

Even if Instagram users sometimes face random issues, this remains one of the most popular social media platforms. To prove it, take a look at the following statistics:

As you can see, Instagram is the fourth most popular social platform worldwide, after Facebook, Youtube, and Whatsapp. According to the 2021 study, Instagram registered a total of 1.300 million global active users.

So, no matter how many issues it can bring up, our presented app will always be on top of the most-used social media tools.

You’ve already seen some potential solutions that might help you fix the Sorry something went wrong Instagram error. However, if you notice that your Instagram account is already connected to a Facebook page, reconnecting the accounts can resolve the issue and this isn’t the only tip to apply.

Do you have any others questions regarding the above procedures? Feel free to share them with us by simply leaving a comment in the dedicated section below.

Restoro has been downloaded by 0 readers this month.

When deploying my rails app to heroku i get the following error:

I checked the logs with:

It shows a lot of syntax errors:

However, in my development mode, I have no syntax errors and everything works fine.

Here is the part of the code giving the syntax error:

In Chrome, dev tools i get a 500 error

Note: I have installed the rails 12 factor gem in the production env, i still get this error. This code works as is in development mode with no syntax errors. Any ideas/help please?

1 Answer 1

As the error says, you have a syntax error in your hash:

In particular, you cannot define symbol hash keys with an appended : when those keys contain a hyphen. (This should be true regardless of environment since its a Ruby syntax issue, so your comment that it works in development is odd.) Instead, you have to define those hash key-value pairs using the old => :

Note that Rails also supports defining data-* attributes with a nested hash:

This does not work for arbitrary hyphenated attributes, however.

Heroku Error? We’re sorry, but something went wrong. We’ve been notified about this issue and we’ll take a look at it shortly heroku

Hi I wonder why one of our pages is in trouble.

I run heroku logs in our cli

And this is the output:

I really don’t know what happened? When I’m browsing http://peekbox.tv/bo

The error still appears.

Should i run heroku rake db:migrate to heal the errors or any other solutions

We’re totally in trouble.

2 Answers 2

Trending sort

Trending sort is based off of the default sorting method — by highest score — but it boosts votes that have happened recently, helping to surface more up-to-date answers.

It falls back to sorting by highest score if no posts are trending.

Switch to Trending sort

The actual error is a couple of lines down:

Therefore one of your post objects has a poster that is nil. Experiment in the console on Heroku ( heroku run console ) and see if you can find the post that doesn’t have a poster.

Putting my «comment» here so the text can be formatted properly. From the terminal try:

This should get you started. Your error is showing that post.poster is nil and you want to find out why.

But I agree with @ryanbigg that you need to learn the basics. Judging from your experience level this might not be something you can figure out on your own.

Resolved We’re sorry, but something went wrong.

Solarom

New Pleskian

I am trying to deploy a NodeJS application on my server, but an error message appears.
I tested several solutions found on the web, but none worked.

IgorG

Forums Analyst

Solarom

New Pleskian

Okay, I have pull a NodeJS application from my remote repository.
I configured the NodeJS extension like this.

Only, when I wish to access my domain: «api.as-sellerie.fr», an error appears with the code «c61ecbaf».

In the domain logs, an error 500 :

Honestly, I’m a brand new Plesk customer and I use Google Translate to communicate in English, lol.

If you have an idea, or a hypothesis, I am interested. I keep looking for the answer to the problem in the meantime, and come back to you if I have an idea.

Solarom

New Pleskian

It’s possible not to use phusion passenger?

I found the logs :

[Wed Apr 01 01:32:46.549460 2020] [autoindex:error] [pid 444:tid 140497834174208] [client 192.168.1.1:56202] AH01276: Cannot serve directory /var/www/vhosts/as-sellerie.fr/api.as-sellerie.fr/: No matching DirectoryIndex (index.html,index.cgi,index.pl,index.php,index.xhtml,index.htm,index.shtml) found, and server-generated directory index forbidden by Options directive

I tried this, it didn’t work

IgorG

Forums Analyst

What is the output of command:

Solarom

New Pleskian

_____________________________________________________________________________________________
*****************************************************************************************************

In the file manager, I clicked on «as-sellerie.fr«.

Then I go to the files for my subdomain and i add the file .htaccess.

My website appears with an error 500.

Here is the log.

[Wed Apr 01 16:34:04.627038 2020] [core:alert] [pid 19115:tid 140497996625664] [client 192.168.1.1:57794] /var/www/vhosts/as-sellerie.fr/api.as-sellerie.fr/.htaccess:

Solarom

New Pleskian

PhusionPassenger did not detect the startup file «app.js«.
For the proper functioning of the application you must create a file server.js which creates a server by pointing your file app.js.

Do not specify listening on a strict number as I have been able to do.

For example, for PhusionPassenger to work, write:
http.createServer(app).listen(process.env.PORT);

And not :
http.createServer(app).listen(5000);

Thank you Igor for the time you spent trying to find a solution. I hope my post will help other users.

Network Monitor «We’re sorry, but something went wrong»

FINAL UPDATE: The issue has been resolved.

UPDATE 10/5/2016 7:45 PST: There is an active problem on Spiceworks HQ’s end that is preventing anyone running Network Monitor from logging in.

Just ran into this problem today, but haven’t opened Network Monitor since last week so no clue how long the problem has been going on.

After attempting to log in to Network Monitor I get a screen that just says «We’re sorry, but something went wrong».

This is occurring on 3 different Network Monitor servers in 3 different sites.
I’ve upgraded each install to 1.5.00111
I’ve uninstalled and reinstalled Network Monitor
Each server is running Server 2012 R2 or 2016 TP4
I am able to access http(s)://frontend.spiceworks.com from each server

Popular Topics in Spiceworks General Support

70 Replies

Me too facing same problem. not much details available even in google search. contacted Spicework team

Glad it’s not just me. This started today. Sounds like something at Spiceworks HQ went screwy 🙁

Same problem here.

Same problem also here today

Same problem here 🙁

Same problem here 🙁

same issue with me as well..Please inform me if anyone got solution.

OK, well good to know that I’m not the only one. Hope this gets resolved soon.

Same problem here. reinstalled same result as the OP

The services not restarting, or stopping, properly is a known bug that we are close to fixing. The «We’re sorry, but something went wrong» message is new. I haven’t seen that before, but I’m able to reproduce this on two separate installs on my end. I’m looping in our dev team and marking this high priority until we get it figured out.

having the same problem and was wondering if it was just me

Same here. Too bad I had to reinstall again thinking it was just me 🙁

Seems I will have to do the configuration all over!

Same thing is happening to me.

Yes been running for a long time now getting same error. Add this to the very long list of bugs in Network Monitor

Have 3 separate installs on separate networks, all showing the same.

Is it fixed yet?? 😀

Same problem here.

Same problems here. Wireshark captures seem to indicate a problem on the Spiceworks cloud.

Same problem here

I opened a ticket with Spiceworks and their team is working on it regarding authentication.

Same problem here. At first I thought one of my backups messed something up last night as I was changing around my backup settings. Did a Network Monitor VM restore to a few days ago, that didn’t work. Did a VM restore to a week ago and that didn’t work. Came to Google, put in the error msg and sorted it the results by date and found this at the top. I’m glad I’m not the only one having this problem.

I have tried installing an older version with the same result.

I’m sure you will find them, but if you want me to let you know of any do give me a shout.

Jaime D (Spiceworks)

I have tried installing an older version with the same result.

Posted this on my way out the door last night, checked this morning to my phone blown up. Glad (maybe not the right word) that it wasn’t just me.

I’ve edited my OP to say that this is a global issue on Spiceworks HQ’s end.

Having the same issue with the services not «stopping» and same error «Something went wrong». The services issue has been happening alot in the last few days. The Spiceworks Event Processor is the service showing «stopping». I have to kill the service and restart it.

I feel so blind without Network Monitor up and running. I think I will go hide in a corner until it’s fixed.

Is there an official notice on this? Status page etc?

My network monitor alerts started coming through now.

My network monitor alerts started coming through now.

I’m back up too. Nice work!

Can you guys try logging in and let me know if it works?

If you haven’t already.

Can you guys try logging in and let me know if it works?

If you haven’t already.

Mine is Now Working, as 11am US Central Time

Looks like it’s solved.

Noa Solution is an IT service provider.

Sweet! Thanks for confirming that for us!

I’m back up, thanks guys!

I’m back in, thanks!

This topic has been locked by an administrator and is no longer open for commenting.

To continue this discussion, please ask a new question.

Read these next.

Building a better IT toolbox

Hi all,Been banging my head against a wall for this one.We’ve got an organisation with two type of people. Group A and Group B we’ll call them.Group A needs to see Group B in their address lists, however, not see anyone but themselves from Group A.Group B.

Can a professional network security assessment be done with just F/OSS tools?

I tend to doubt it. To have a professional quality security assessment, you would need to scan for the latest vulnerabilities. I am not sure if any free tool is kept that up-to-date. Maybe I’m wrong.Maybe with the correct combination of tools? OpenVAS, Me.

Snap! PyPI phishing, Twilio breach, VPNs, Artemis I, photos of the moon, & more

Your daily dose of tech news, in brief. Welcome to Monday, everyone! On August 29, 1990, the Computer Misuse Act became the United Kingdom’s legal defense against hacking and criminalized several acts, including accessing data without authorization.

We re sorry but something went wrong

Профиль
Группа: Участник
Сообщений: 1
Регистрация: 8.6.2012

Репутация: нет
Всего: нет

Здравствуйте. Без вашей помощи, дорогие специалисты, не могу обойтись.

После запуска rake assets:precompile при запуске в окружении production вижу, как сайт извиняется http://petromi.com/get/9ac77e194e.png

При запуске в окружении development показывает следующее http://petromi.com/get/bb6bbb0af9.png

Showing /home/virtwww/w_office-trend-ru_c209ba3b/http/app/views/public/_main_menu.html.erb where line #12 raised:

undefined method `transliteration’ for nil:NilClass
Extracted source (around line #12):

В чём я допустил ошибку? Как её исправить? Как поднять сайт обратно?

Шустрый

Профиль
Группа: Участник
Сообщений: 122
Регистрация: 20.10.2007
Где: Воронеж

Репутация: нет
Всего: 2

Опытный

Профиль
Группа: Участник
Сообщений: 491
Регистрация: 24.3.2005
Где: Ode$$a

Репутация: нет
Всего: 2

простите меня пожалуйста, но я не могу удержаться Сообщения с сайта на почту пользователю

j2FunOnly, этот вопрос фрилансерам решить не удается. Иначе я бы не просил помощи здесь, заведомо ничего не понимая в программировании.

Добавлено через 51 секунду
Nameless One, объясните, пожалуйста, где их искать?

Nameless One, не знаю, как это делать

логи нашел вот такие (не знаю, те или не те, нашел в нете, что надо смотреть именно в логах с таким именем)

Вложения

logs.zip (584.0 Кб, 3 просмотров)

Something went wrong when installing Prey
Something went wrong when installing Prey. Please make sure on other installations are ongoing. For.

SMOG SETTINGS WRONG
Подскажите пожалуйста кто знает.. материнка Асус P5LD2SE не грузиться комп.. выключился.

CMOS Setting Wrong.
Всем добрый день,у меня с пк такая трабла: 1.Решил коече изменить в биосе,связано с юизби,я.

Wrong FireBird Binaries
Добрый день! Не подскажите почему у меня вылетает ошибка: Пытаюсь обновить Motiw 1.1 до 1.2.

«We’re sorry but something went wrong please try again» when enabling testing/simulator for Smart Home action

When enabling testing of my Smart Home action for an old project I get «we’re sorry but something went wrong please try again» and my Smart Home action does not show up for linking in the Google Home app.

I created a new project and I can enable testing mode for it. However, I would like to use my old project as I have set up several services/APIs (like report state) that I would prefer not to set up from scratch on a new project.

Any way to know why I am getting «we’re sorry but something went wrong please try again» and/or figure out what is different between my old and new projects that makes the old not work?

My old application was responding to Google Assistant commands but I had to unlink ir because re-sync’ing my smart home devices was failing. After unlinking I am not able to re-link because I cannot get my application in testing mode due to this problem.

Fatal error & uncaught error with WooCommerce Product Bundles plugin #5338

Comments

Orhn commented Aug 8, 2018

Prerequisites

Description

Fatal error, uncaught error, when using WooCommerce Product Bundles plugin. It was working with RC4.

Steps to reproduce

Isolating the problem

Environment

== Server Environment ==
Operating System: Linux
Software: nginx/1.10.1
MySQL version: 5.6.37
PHP Version: 7.1.7
PHP Max Input Vars: 4000
PHP Max Post Size: 1000M
GD Installed: Yes
ZIP Installed: Yes
Write Permissions: All right
Elementor Library: Connected

== WordPress Environment ==
Version: 4.9.8
Site URL: https://ecommerce-v2.local
Home URL: https://ecommerce-v2.local
WP Multisite: No
Max Upload Size: 300 MB
Memory limit: 40M
Permalink Structure: /%postname%/
Language: en-US
Timezone: Europe/Stockholm
Debug Mode: Inactive

== Theme ==
Name: Elementor Hello Theme
Version: 1.0
Author: Elementor Team
Child Theme: No

== User ==
Role: administrator
WP Profile lang: en_US
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_6) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/11.1.2 Safari/605.1.15

== Active Plugins ==
Elementor
Version: 2.1.6
Author: Elementor.com

== Must-Use Plugins ==
Local by Flywheel Relative URL (for Live Links)
Version: 1.0
Author: Flywheel

Error

Fatal error: Uncaught Error: Call to a member function is_type() on string in /app/public/wp-content/plugins/woocommerce-product-bundles/includes/class-wc-pb-display.php:294 Stack trace: #0 /app/public/wp-includes/class-wp-hook.php(286): WC_PB_Display->add_edit_in_cart_notice(») #1 /app/public/wp-includes/class-wp-hook.php(310): WP_Hook->apply_filters(», Array) #2 /app/public/wp-includes/plugin.php(453): WP_Hook->do_action(Array) #3 /app/public/wp-content/plugins/elementor-pro/modules/woocommerce/documents/product.php(133): do_action(‘woocommerce_bef. ‘) #4 /app/public/wp-content/plugins/elementor-pro/modules/theme-builder/classes/locations-manager.php(216): ElementorPro\Modules\Woocommerce\Documents\Product->print_content() #5 /app/public/wp-content/plugins/elementor-pro/modules/theme-builder/classes/locations-manager.php(169): ElementorPro\Modules\ThemeBuilder\Classes\Locations_Manager->do_location(‘single’) #6 [internal function]: ElementorPro\Modules\ThemeBuilder\Classes\Locations_Manager->ElementorPro\Modules\Them in /app/public/wp-content/plugins/woocommerce-product-bundles/includes/class-wc-pb-display.php on line 294

The text was updated successfully, but these errors were encountered:

Receive «We’re sorry, but something went wrong.» error when attempting to sign CLA #104

Comments

joelrbrandt commented Feb 26, 2015

After I authenticate with GitHub, fill out the form, and click «submit», I get an error that says «We’re sorry, but something went wrong.»

This happens both in Chrome (40.0.2214.115 (64-bit)) and Safari (Version 8.0.3 (10600.3.18))

I’m filling the form with this information:

The text was updated successfully, but these errors were encountered:

dionyziz commented Feb 26, 2015

I get an HTTP 500 error which I don’t know if it’s the same. Here’s a screenshot of the error.

This occurs after the form is POSTed. The details I entered are:

Email: dionyziz@kamibu.com
Name: Dionysis Zindros
Country: Switzerland
Type «I AGREE»: I AGREE

rwaldron commented Feb 26, 2015

Don’t laugh—I can’t sign the CLA for JSHint.

mattflaschen commented Feb 27, 2015

I get the same error, in both Firefox and Chromium.

schuyler1d commented Feb 27, 2015

I also get the same error (also need to sign CLA for JSHint).

dionyziz commented Feb 27, 2015

I ended up signing via GPG.

On Fri, Feb 27, 2015 at 5:17 AM, Schuyler Duveen notifications@github.com
wrote:

I also get the same error (also need to sign CLA for JSHint).

—
Reply to this email directly or view it on GitHub
#104 (comment).

victor-homyakov commented Feb 27, 2015

FAIL. Can’t sign the CLA.

subnetmarco commented Feb 27, 2015

bollwyvl commented Feb 28, 2015

fabiomcosta commented Feb 28, 2015

I had the same issue

svendahlstrand commented Mar 1, 2015

jugglinmike commented Mar 1, 2015

Would anyone subscribed to this issue mind hopping back over to https://www.clahub.com/agreements/jshint/jshint and trying to sign again? @stevenbenner just successfully signed (thanks, Steven!), and I’m cautiously optimistic that this has magically fixed itself (especially since the webhook handler seems to be working as well)

joelrbrandt commented Mar 2, 2015

@jugglinmike Works for me! Closing this issue.

subnetmarco commented Mar 2, 2015

The bug is still there when I try to sign at https://www.clahub.com/agreements/Mashape/kong

subnetmarco commented Mar 2, 2015

To give some more context, below is the snapshot of my form. I am also the creator of the CLA, so the issue may be related to owners signing their own CLAs.

jugglinmike commented Mar 2, 2015

@thefosk I’m not so sure about that—I was the first to sign my project’s CLA. Then again, @rwaldron is also an owner of the GitHub repository (but not the license on CLAHub), and he couldn’t sign. It might be that he triggered the bug when he first attempted to sign.

@rwaldron: do you remember if you commented here immediately after attempting to sign?

jasonm commented Mar 5, 2015

Hm, yes there are errors logged for these. Here’s a redacted subset for some of the JSHint-related ones: https://gist.github.com/jasonm/761b3d3d25aa697d3cda

Interestingly the access_token that I redacted from those logs doesn’t appear attached to any CLAhub user; I’d expect it to be @jugglinmike ‘s token, i.e the owner of the Agreement. @jugglinmike did you go through the OAuth flow anew recently?

If so, @thefosk have you gone through a new OAuth flow to get the reduced scopes for #101? If not, could you try visiting https://clahub.com/sign_out and then signing in fresh, and see if that (1) sets the reduced GitHub OAuth scope, and (2) fixes this issue?

jasonm commented Mar 5, 2015

If this is the case, then it is only the owner of the repo whose auth token needs to be updated, not every signer.

jugglinmike commented Mar 5, 2015

@jasonm I can’t say for sure :/ I did not create the CLA for JSHint until after gh-101 was deployed, but I already had an account with CLAHub. It sounds like this is related to my account and not necessarily tied to any specific license.

subnetmarco commented Mar 5, 2015

@jasonm I confirm that after signing out, accepting the new OAuth scopes, and signing the CLA again it finally worked.

nijikokun commented Apr 28, 2015

New user registering on CLAHub I have this issue @jugglinmike I am not the owner.

Hundreds of people wanting to sign our CLA are having this issue.

jugglinmike commented Apr 28, 2015

@nijikokun You might try de-authorizing CLAHub from the GitHub administrative interface, then completely signing out of both CLAHub and GitHub and then signing in again. The owner of the CLA should try the same (in that case, de-authorizing may delete the existing CLA—you should confirm with the maintainers before trying that if you already have signatures). This may or may not have been what fixed the issue for me.

That’s about as much assistance as I can provide. If things still don’t work for you, then @jasonm is probably your best bet—he is the maintainer of CLAHub ( and a swell guy 🙂 )

Footer

© 2022 GitHub, Inc.

You can’t perform that action at this time.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.

GitLab 500: We’re sorry, but something went wrong [closed]

Part of GitLab Collective

This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.

500: We’re sorry, but something went wrong.

/home/git/gitlab/log/production.log:

1 Answer 1

It seems to be linked to the python you are using:

The last 3 issues with an exception on the blob.colorize line were fixed by reinstalling/updating python or making sure /usr/bin/env python was >= 2.5 and

Not the answer you’re looking for? Browse other questions tagged gitlab or ask your own question.

This question is in a collective: a subcommunity defined by tags with relevant content and experts.

Related

Hot Network Questions

By clicking “Accept all cookies”, you agree Stack Exchange can store cookies on your device and disclose information in accordance with our Cookie Policy.

Customizer: We’re sorry, but something went wrong. [SOLVED]

Please Login to Comment

Hi,
I’ve made and uploaded a couple of customizable things and apart from that I would like to use 2018 features it always went well, until this file
https://www.thingiverse.com/thing:3353517
There is an error message «We’re sorry, but something went wrong.» I suspect that I might have used language features that aren’t compatible with customizer even if the file renders on OpenSCAD 2015.03-3. What could it be?
Thanks!
Benjamin

Edit: as suggested by wstein, it was an UTF-8 related problem.

hey I’m new to this but I just made an echo dot Millenium Falcon case when I click on it it just said sorry something went wrong so it similar but not the same issue

The way to find out what’s wrong usually is to strip away parts from your code and try the rest until it works.

The part that you stripped before it started working can then be considered the problematic one.

Slow going, but if none of the usual suspects is responsible for the problem, that will work even if it lacks elegance 😉

It works for me, changed every parameter there is (see picture test.png).
It is possible that it has to do with the very slow response times Thingiverse suffers from the last month or so. See https://www.thingiverse.com/groups/thingiverse/forums/site-issues-and-feedback/topic:33945#comment-2271637 for a solution for that.

change line 152 this way and it works:

text(text=str(«angle: «, corpus_angle, «\u00B0»), size=outerDiameter*0.18, valign = «top»);

The degree char is unicode U+00B0. Maybe Customizer parser can’t handle UTF-8 source correct.

Heroku logs reveal no errors yet most of my URLs read «We’re sorry, but something went wrong.»

My app works wonderfully on my local machine but when I create my first post after pushing the app to Heroku I get «We’re sorry, but something went wrong.» on every page except /posts/new The heroku logs command reveals:

Heroku customer service isn’t available today due to the holiday. I was wondering if anyone knows how I might troubleshoot this. I have expanded logging enabled.

2 Answers 2

Trending sort

Trending sort is based off of the default sorting method — by highest score — but it boosts votes that have happened recently, helping to surface more up-to-date answers.

It falls back to sorting by highest score if no posts are trending.

Switch to Trending sort

This is not a direct answer to the question above, but more for the related issue of why logs on Heroku are not detailed enough.

For those who arrive at this SO post, as I did, because they have sparse logs and can’t understand why, and have Rails 4, note that you need the rails_12factor gem in your Gemfile in order to get detailed debug level logs in your Heroku logs. Essentially, adding the gem enables STDOUT logging in Rails4, without which your debug level logs information is not passed into the Heroku logs.

«We’re sorry but something went wrong please try again» when enabling testing/simulator for Smart Home action

When enabling testing of my Smart Home action for an old project I get «we’re sorry but something went wrong please try again» and my Smart Home action does not show up for linking in the Google Home app.

I created a new project and I can enable testing mode for it. However, I would like to use my old project as I have set up several services/APIs (like report state) that I would prefer not to set up from scratch on a new project.

Any way to know why I am getting «we’re sorry but something went wrong please try again» and/or figure out what is different between my old and new projects that makes the old not work?

My old application was responding to Google Assistant commands but I had to unlink ir because re-sync’ing my smart home devices was failing. After unlinking I am not able to re-link because I cannot get my application in testing mode due to this problem.

Если вы являетесь владельцем приложения, проверьте журналы для получения дополнительной информации. Ошибка 500

Я создал страницу в rails с формой SignUp, и она отлично работает локально, все было хорошо, поэтому я развернул проект в Heroku, где static_page работает отлично, но эта форма не работает и выдает мне ошибку:

We’re sorry, but something went wrong.

If you are the application owner check the logs for more information.

Итак, я просмотрел журнал, где все загружается нормально, пока это не становится красным:

2020-01-26T02:13:09.077537+00:00 heroku[router]: at=info method=GET path=»/signup» host=safe-shelf-03588.herokuapp.com request_id=a96a3ba1-41ed-4963-8f6a-5cd3676954ff fwd=»181.115.249.233″ dyno=web.1 connect=0ms service=5ms status=500 bytes=1891 protocol=https

Я просмотрел форумы, и наиболее логичной причиной было просмотреть маршруты, но ошибка 500 является очень распространенным кодом проблемы по разным причинам, и мне не повезло.

Задачи

Сохранённые запросы

Bug #12305

foreman-one We’re sorry, but something went wrong.

Описание

I’m getting this error after adding formen-one plugin and trying to edit one of the compute profile (small/medium/large).
After choosing the size, I click on the computer resource (for opennebula) and get:

We’re sorry, but something went wrong. We’ve been notified about this issue and we’ll take a look at it shortly.

История

#1 Обновлено Eyal Maran почти 7 года назад

Sorry, just realized it’s in digital-ocean plugin part.. I don’t know how to move it to the correct one..

#2 Обновлено Аноним почти 7 года назад

The ONE plugin seems not to be maintained by the original authors at the moment and is broken since at least Foreman 1.8. I’ll try to contact the authors and see what’s the status.

#3 Обновлено Tim Verhoeven почти 7 года назад

I’m having the same issue. Basically it looks like the API for plugins and more specific compute resources has been changing in newer Foreman releases and the plugin has been updated to follow.

I’ve got the error above fixed my moving a file, but then another error popped up. I really could use this plugin back in working order so I’m willing to take a shot at updating it. But is there some documentation somewhere documenting the changes in the API since Foreman 1.5? Else it would be a bit difficult for me since I’m not a Foreman developer, just an avid user 😉

#4 Обновлено Eyal Maran почти 7 года назад

Tim Verhoeven wrote:

I’m having the same issue. Basically it looks like the API for plugins and more specific compute resources has been changing in newer Foreman releases and the plugin has been updated to follow.

I’ve got the error above fixed my moving a file, but then another error popped up. I really could use this plugin back in working order so I’m willing to take a shot at updating it. But is there some documentation somewhere documenting the changes in the API since Foreman 1.5? Else it would be a bit difficult for me since I’m not a Foreman developer, just an avid user 😉

In /usr/share/foreman/bundler.d/Gemfile.local.rb: gem ‘foreman_one’, :git => «https://github.com/b0e/foreman-one»

It seems to be working fine. I didn’t have much time to test it, but at least I don’t get the same error as before.

#5 Обновлено Tim Verhoeven почти 7 года назад

Thanks for the hint. Using that fork I get a lot further along. But I still can’t save a compute profile. Now I get this error:

But we are getting close 😉

#6 Обновлено Mike Fröhner почти 7 года назад

this error look familiar. I think I had this error too, before using that fork which Eyal suggested. Which version of OpenNebula (oned) and foreman are you using?

OpenNebula 4.12.1 & foreman 1.9.3 & the suggest fork of the plugin.

I try to create a host on my oned cluster throught foreman/hosts/new. After using the fork of foreman_one, it is possible for me to select the configured oned controller for «Deploy on». Foreman is able to fetch to configured templates from OpenNebula and it is also possible to select the virtual network from oned. Something which is strange for me, I have to select the network on the «Interfaces» tab and not at the part of virtual machine. After clicking the «submit» button I get the error:

And after clicking the same button again foreman says «Some of the interfaces are invalid. Please check the table below.» and auto selects the interfaces tab on hosts/new. I figured out the MAC address was not set probably so I manually configured it and saved it. It was saved on foreman’s side the VM has not been created on my oned cluster. I tried to do this again, but before clicking submit I configured the mac address manually: same behavior. I’ll attach the error output.

#7 Обновлено Mike Fröhner почти 7 года назад

Well okay, after reading your message again and playing arround I found out I get the same error you have on saving the compute profile 🙂

#8 Обновлено Mike Fröhner почти 7 года назад

attaching my full strace for saving the compute_profile

#9 Обновлено Tim Verhoeven почти 7 года назад

Ok, so you are indeed getting the same error like I do now.

I’m running Foreman 1.9.3 and OpenNebula 4.14.0.

I’m not enough of a developer to figure this one out myself. So hopefuly the created of this latest version can help us.

#10 Обновлено Tim Verhoeven почти 7 года назад

I’ve opened 2 issues on the foreman-one github to track the actual issues I’m seeing. The current head from the foreman-one includes all the work from the b0e/foreman-one fork. But at least with this version I’m already seeing the VM and templates on the OpenNebula side. Se we are making progress.

#11 Обновлено Аноним больше 6 лет назад

what’s the status here with foreman_one 0.4?

#12 Обновлено Mike Fröhner больше 6 лет назад

Michael Moll wrote:

what’s the status here with foreman_one 0.4?

I tested 0.4 via adding:

gem ‘foreman_one’, :git => «https://github.com/theforeman/foreman-one.git»

gem «fog», :git => «https://github.com/netways/fog.git», :branch => «net-v1.33.0»

I am running foreman 1.11 and OpenNebula 4.14.2 and I still do have the them behavior, which I reported 6 month ago:

And after clicking the same button again foreman says «Some of the interfaces are invalid. Please check the table below.» and auto selects the interfaces tab on hosts/new. I figured out the MAC address was > not set probably so I manually configured it and saved it. It was saved on foreman’s side the VM has not been created on my oned cluster. I tried to do this again, but before clicking submit I configured the mac address manually: same behavior. I’ll attach the error output.»

#13 Обновлено Аноним больше 6 лет назад

Plase use our packages in the respective yum/apt repos, or at least use the fog version coming with Foreman.

In another note: As I already mentioned in multiple GitHub issues, it would be great to have a fog-one repo split out and maintained by people using one to get in fixes more easy and use it on gems like foreman_one.

Cloned a RoR server and now getting «we’re sorry, but something went wrong error»

I have a working RoR app that’s running on Ubuntu Server, served by Nginx and Unicorn. It’s using a local postgres database. I also think it’s running on Sinatra instead of rails, but I’m too new to RoR to be able to say for certain.

I am attempting to create a development copy of the app to do some testing with. I’m able to do so using the source code, bundle install, and then running webbrick on my desktop. However, my developer wants to duplicate the environment that the actual production copy is running in. I cloned the server hosting the application, but when I browse to the server I get the dreaded «We’re sorry, but something went wrong» error.

Here’s what I’ve checked so for. I looked at the log files in the app/logs directory, and those haven’t been updated in the last 6 days, so I suspect nothing relevant will be in them. If I run «service nginx status», it appears to be started. The database is running, and I can access it through the psql interface. Again, I’m pretty much an RoR newb. I was hoping one of you kind folks might give me some advice. Where should I look next? I’m sure it’s something simple that I’m just overlooking. Thanks in advance!

We’re sorry, but something went wrong. #581

Comments

PPantaz commented May 4, 2018

After couple days of Postal running, I attempt to login and land on this page

«We’re sorry, but something went wrong.
If you are the application owner check the logs for more information.»

The text was updated successfully, but these errors were encountered:

Manishjodhani commented May 7, 2018 •

Restart mysql, ngnix and postal services
Then try

willpower232 commented May 7, 2018

If restarting the services didn’t help, have a look in your log files /opt/postal/log.

I see this error if there has been a problem in the code because the database has done something screwy.

PPantaz commented May 7, 2018

restarting nginx and postal fixes the issue.

PPantaz commented May 9, 2018

Issue is back. After couple days of smooth operation, i land back to that page when attempting to login.
«We’re sorry, but something went wrong.
If you are the application owner check the logs for more information.»

Will verify log

PPantaz commented May 9, 2018

Here the reason, the DB crashes. Any idea if its a memory issue, perhaps my server needs more ram?

May 08 04:29:50 mail1 mysqld[7751]: 2018-05-08 4:29:50 139767082703104 [ERROR] InnoDB: Cannot allocate memory for the buffer pool
May 08 04:29:50 mail1 mysqld[7751]: 2018-05-08 4:29:50 139767082703104 [ERROR] Plugin ‘InnoDB’ init function returned error.
May 08 04:29:50 mail1 mysqld[7751]: 2018-05-08 4:29:50 139767082703104 [ERROR] Plugin ‘InnoDB’ registration as a STORAGE ENGINE failed.
May 08 04:29:50 mail1 mysqld[7751]: 2018-05-08 4:29:50 139767082703104 [Note] Plugin ‘FEEDBACK’ is disabled.
May 08 04:29:50 mail1 mysqld[7751]: 2018-05-08 4:29:50 139767082703104 [ERROR] Unknown/unsupported storage engine: InnoDB
May 08 04:29:50 mail1 mysqld[7751]: 2018-05-08 4:29:50 139767082703104 [ERROR] Aborting
May 08 04:29:50 mail1 systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE
May 08 04:29:50 mail1 systemd[1]: Failed to start MariaDB 10.1.32 database server.
May 08 04:29:50 mail1 systemd[1]: mariadb.service: Unit entered failed state.
May 08 04:29:50 mail1 systemd[1]: mariadb.service: Failed with result ‘exit-code’.

willpower232 commented May 9, 2018

If it won’t start, its probably memory related unless you have loads already.

You may also be interested in the MySQL/Maria configuration changes here #324 (comment)

PPantaz commented May 15, 2018

Worst MTA ever, horrible. Plus the docs are not straight forward, not explained well, and not configured well. Very unstable platform, deleting it for the 2nd time, trashing my digital ocean server again. SCRAP

PPantaz commented May 15, 2018

Ridiculous, i can’t stop thinking about how this POSTAL busts so much, and your docs dont even explain it well, dont even reply to this post

Footer

© 2022 GitHub, Inc.

You can’t perform that action at this time.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.

Cannot access «Scans» : We’re sorry, but something went wrong. #45

Comments

treuss commented Nov 25, 2013

Best regards,
Thomas

Here’s the debug log:

The text was updated successfully, but these errors were encountered:

Zapotek commented Nov 25, 2013

Could you also send me the system/logs/webui/production.log file please?
Also, when you said upgrade, did you mean that you used the arachni_web_import script?

Zapotek commented Nov 25, 2013

Also, which nightlies? Because I remember seeing this in the nightlies a few weeks ago but then I fixed it. Does this happen with the latest nightlies?

treuss commented Nov 25, 2013

The nightlies I used for the upgrade were those available for download this afternoon.

Zapotek commented Nov 25, 2013

Hm, I see, Would you mind deleting the log and reproducing then?

treuss commented Nov 25, 2013

Ok, I’ve got a log (24K). Shall I paste it in here?

On Mon, Nov 25, 2013 at 4:53 PM, Tasos Laskos notifications@github.comwrote:

Hm, I see, Would you mind deleting the log and reproducing then?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/45#issuecomment-29212708
.

mailto: thomas.reuss@gmail.com
mobil: +49-177-4253751
home: +49-9367-413370

Zapotek commented Nov 25, 2013

Better make a gist out of it.
Also, I forgot to ask, from which version did you upgrade?

treuss commented Nov 25, 2013

The VERSION file says: 1.0dev-1.0dev (ctime on the particular system is Oct 1st). Does that help in any way?
I remember using a nightly build.

Zapotek commented Nov 25, 2013

Ah, got it. Thanks man, I’ll probably have a fix for you today, although it may take me a couple of days to push fresh nightlies (having some ISP issues).

I didn’t catch this myself because I test the arachni_web_import functionality last, once I’m sure that the DB schema changes I’ve made during development are solid.

One more thing, better test nightlies by themselves and not upgrade to or from them as schema changes or migrations may be changed during dev in a way that could leave you with a corrupted DB.
Or you could use a test DB do to that so even if something blows up you won’t be left high and dry.

treuss commented Nov 25, 2013

That’s no problem 😉

I see: Schema updates are always tricky o.O

Zapotek commented Nov 25, 2013

If you are talking about the issues you had reported in the past those were indeed fixed, this is a new one and it is related to schema changes. A new field has been added, which ends up being nil for scans of previous versions and that makes the page blow up.

I’ll take care of it, no worries.

treuss commented Nov 25, 2013

Yes, it’s a new issue, definitely. Back then, the problems were solved.
Today, I just cleared some out-of-date scans, when the issure appeared.

Показать полную ошибку в браузере в Ruby on Rails

Я начал учиться Rails сегодня. Я следую онлайн-учебнику. Я получаю сообщение об ошибке. В учебнике всякий раз, когда возникает ошибка, причина ошибки отображается в браузере. Но я просто получаю это сообщение:

We’re sorry, but something went wrong. If you are the application owner check the logs for more information.

разработка.рб

журнал

config.ru

приложение.rb

Это ошибка в среде разработки или в рабочей среде?

насчет env не знаю. Как я могу это проверить?

Как вы запустили сервер rails?

Я набрал команду rails server в терминале.

Не могли бы вы перезапустить сервер и показать мне журнал, что он показывает?

Настройка consider_all_requests_local = true — это правильный способ отображения трассировки стека в браузере. В 99% случаев вы не хотите сделать это в рабочей среде, так как это раскрывает внутреннюю реализацию (потенциально конфиденциальную) детали вашего сервера.

Журнал показывает Rails version application starting in development эту линию разработки или что-то еще?

Я добавил полный журнал, отображаемый при перезапуске сервера.

Нет. Я ничего не менял в этих файлах. Я также добавил эти файлы.

Error: We’re sorry, a server error occurred. Please wait a bit and try again. (line 303, file «Code», project «FirebaseApp») #23

Comments

derrickrc commented Aug 23, 2019

I started getting this error last night on a script that had been triggering fine all day. I’m not sure what the issue is, can you please advise? Thanks.

The text was updated successfully, but these errors were encountered:

derrickrc commented Aug 23, 2019

OK, it seems to be working on my personal gmail and not my gSuite, I must have hit some limit yesterday. What are the limits? When will this reset? Midnight has come and gone my time and it’s still throwing the error. Thank you.

vn78dev commented Oct 1, 2019

I started getting the same error today. Nothing really changed in the code or scopes, but Stackdriver log refers to the FirebaseApp library.

derrickrc commented Oct 1, 2019

I started getting the same error today. Nothing really changed in the code or scopes, but Stackdriver log refers to the FirebaseApp library.

Is it possible you hit the Apps Scripts usage limit for urlfetch calls?

vn78dev commented Oct 1, 2019

no way, I ran fetches sort of 2 or 3 times today..

vn78dev commented Oct 1, 2019

see if this screenshot helps, looks like «line 234» refers to the FirebaseApp code, not mine:

derrickrc commented Oct 1, 2019

It looks like that’s the line for throwing a generic error, hence why we don’t get more detail on the error. I just ran my code and it executed. I’d try running it on a different gmail account to confirm you didn’t exhaust your quota. Good luck.

vn78dev commented Oct 1, 2019

If this helps with any ideas what might be wrong, I’d appreciate your help very much.

vn78dev commented Oct 2, 2019

Solved it. The library error was triggered by the pair
«urlFetchWhitelist»: [«https://www.example.com/»]
in my manifest json. Once I removed it, requests became successful.
I am not sure whether it’s a library problem though.

affordablequalityhomes commented Apr 14, 2020

I’m getting the same error, in FirebaseApp_._sendAllRequests

So as per the comment above, I tried:

and that gave me a different error:

marcomow commented Nov 25, 2020 •

I suggest @RomainVialard to add these scopes into the original library, this will have also the nice side-effect of non constraining the users of the library to manual update of the scopes.

vn78dev commented Apr 13, 2021

RomainVialard commented Apr 16, 2021

dginovker commented Dec 8, 2021 •

I created a general purpose function based on Romain’s answer above. This will solve your «server error occurred» if the problem is you’re pulling too much data:

If any single child is over 50Mb, this solution won’t work and you’ll have to do something else

Redmine

We’re Sorry, but something went wrong

Bitnami Redmine 3.1.0-0
Ubuntu 14.04.2

Redmine has been working for years, with no issue. I know a few Linux commands, from a college class. so I have no real skills in troubleshooting. Anyone have anything I can try??

At first the «Projects» start saying Internal Error. I rebooted the server and now the homepage has the error below

We’re sorry, but something went wrong.

We’ve been notified about this issue and we’ll take a look at it shortly.

Information for the administrator of this website

The Phusion Passenger application server encountered an error while starting your web application. Because you are running this web application in staging or production mode, the details of the error have been omitted from this web page for security reasons.

Please read the web server error log to find the details of the error. If you don’t know where the web server error log is, read the troubleshooting documentation below.

Alternatively, you can turn on the «friendly error pages» feature (see below), which will make Phusion Passenger show many details about the error right in the browser.

Phusion Passenger troubleshooting documentation:
•Nginx integration mode
•Apache integration mode
•Standalone mode

Ответы (1)

Hard drive was full. you would think AWS would provide some type of notification when a hard drive is at 80% or 90%, but nope, not even at 100% full.

Redmine

We’re sorry, but something went wrong.

Hello,
I am creating high availability clustering so that I create 3 server (server1, server2,server3) using pacemaker.
I want to add many resources into this servers for example apache redmine etc..
now I have problem running redmine.
I created redmine platform each server. And setup passenger.conf and 000-default.conf

/etc/apache2/mods-available/passenger.conf

PassengerDefaultUser www-data
PassengerUserSwitching on
PassengerUser redmine
PassengerGroup redmine

/etc/apache2/sites-available/000-default.conf

RailsBaseURI /redmine
PassengerResolveSymlinksInDocumentRoot on

I do it in each and every server.
server2 get actual output (redmine homepage)
on server1 i got message «*We’re sorry, but something went wrong.*
We’ve been notified about this issue and we’ll take a look at it shortly.»
on server3 i got Index of /redmine

why I got different output for different server? what is the reason for this kind of output?

3 nodes configured
2 resources configured

Online: [ server1 server2 server3 ]

Full list of resources:

Daemon Status:
corosync: active/disabled
pacemaker: active/disabled
pcsd: active/enabled
root@server2:

Network Monitor: We’re sorry, but something went wrong.

The last thing in the log is:INFO: [49.75 2cdad0]
OpenSSL::SSL::SSLError (An existing connection was forcibly closed by the remote host):
lib/http.rb:82:in `request’
lib/frontend_client/registration.rb:26:in `community_register_check_user’
lib/server/middleware/set_content_length.rb:19:in `call’
lib/active_redis/middleware.rb:14:in `call’
lib/app_stats/middleware.rb:11:in `call’
lib/server/middleware/static_assets_path_rewriter.rb:40:in `call’
lib/server/rails_wrapper.rb:26:in `call’

Align RPOs and RTOs to meet your SLAs

As previously mentioned, we’ve had a few people report this. In order to keep everything centralized, I’m going to lock this topic. Please follow this one for updates: https://community.spiceworks.com/topic/1859302-network-monitor-we-re-sorry-but-something-went-wrong

7 Replies

Can this be merged

I’ve seen nearly a dozen threads about this today. Gonna need a lot of merging.. 🙂

I’ve linked most to one thread and asked for support to join us, however time-zones mean we need to wait for them to wake up

Sorry, we don’t have a merge function otherwise I’d love to make a mega-thread of all these!

Same Problem here.

as far as merging the topic and preventing more repeats, Is there a way to make the title RED instead of black, and Pin it to the top, Or maybe even some kind floating pop-up when users come to the page.

As previously mentioned, we’ve had a few people report this. In order to keep everything centralized, I’m going to lock this topic. Please follow this one for updates: https://community.spiceworks.com/topic/1859302-network-monitor-we-re-sorry-but-something-went-wrong

This topic has been locked by an administrator and is no longer open for commenting.

To continue this discussion, please ask a new question.

Read these next.

Building a better IT toolbox

Hi all,Been banging my head against a wall for this one.We’ve got an organisation with two type of people. Group A and Group B we’ll call them.Group A needs to see Group B in their address lists, however, not see anyone but themselves from Group A.Group B.

Can a professional network security assessment be done with just F/OSS tools?

I tend to doubt it. To have a professional quality security assessment, you would need to scan for the latest vulnerabilities. I am not sure if any free tool is kept that up-to-date. Maybe I’m wrong.Maybe with the correct combination of tools? OpenVAS, Me.

Snap! PyPI phishing, Twilio breach, VPNs, Artemis I, photos of the moon, & more

Your daily dose of tech news, in brief. Welcome to Monday, everyone! On August 29, 1990, the Computer Misuse Act became the United Kingdom’s legal defense against hacking and criminalized several acts, including accessing data without authorization.

«Sorry you’re creating too many entries, try again later» #11

Comments

Senfeld commented Apr 1, 2016

The Auto-Solver worked perfect when I first tried it yesterday. I wanted to test it and I Auto-Solved 10 raffles, more or less.
Today I wanted to Auto-Solve one Instant Win gleam.io, the first one in the whole day, but i got this message: «Sorry, you’re creating too many entries; try again later». My first attempt was to clean my chrome cookies, but it didn’t change anything. Any idea of what I can do?
Great piece of code you created 🙂

The text was updated successfully, but these errors were encountered:

Wrascon commented Apr 1, 2016

Tackyou commented Apr 1, 2016

Hm.. I have the same issue. Proxy doesn’t help. It’s blocked as soon as I log in with my steam account to gleam.io
Maybe they added some limits?

Senfeld commented Apr 1, 2016

@kofe88 It´s not an IP ban, it’s an account ban, once you auth yourself with a social media account you can’t do any tasks.

divit0n commented Apr 1, 2016

yep its account ban..

Tackyou commented Apr 1, 2016

I added a random delay to possibly prevent detection in 1.8.1

sn-o-w commented Apr 1, 2016

I have the same problem as you guys.
I e-mailed hello@gleam.io and they replied «Our fraud filter now actively bans users that are using scripts to enter (since it’s against our TOS). Depending on the severity the ban can be anywhere from 1 month to permanent.» 🙁

ghost commented Apr 3, 2016

11 of my accounts got banned because of this script. Damn! 🙁

The author should make a big red disclaimer:

USING THIS SCRIPT WILL GET YOUR ACCOUNT BANNED.

Senfeld commented Apr 3, 2016

Looks like the ban for the usage of this script is 1 month. That’s what some people got as an answer from Gleam when asking how long the ban would be.
In a month we’ll try again 😄

ghost commented Apr 3, 2016

@djvalen I like your positive attitude. I hope for that too 🙂

Revadike commented Apr 3, 2016

I wonder if you can still win in giveaways you have entered previously, if you are banned. Does somebody know that?

ghost commented Apr 3, 2016

going to remove your script and i will make sure to never use it again :C

Dronstar93 commented Apr 4, 2016

Joaco853 commented Apr 4, 2016

Tackyou commented Apr 4, 2016

It’s a 1 month ban

titoncio commented Apr 4, 2016

Senfeld commented Apr 5, 2016

It would be good to know if with the random delay people still get banned

Wrascon commented Apr 6, 2016

@titoncio Yes No Checking Checking. And then you recommend me?

titoncio commented Apr 6, 2016

Joaco853 commented Apr 7, 2016

no way to continue using gleam, or if there is or wait for the end of the month ban?

DemonAk commented Apr 12, 2016

banned with random delay =, don’t use script

sn-o-w commented Apr 12, 2016

@Tackyou maybe you should disable auto-reveal hidden entries (and auto-completation of hidden entries) to avoid possible detection

DemonAk commented Apr 13, 2016

Our fraud filter now actively bans multi-account abuse.

sn-o-w commented Apr 13, 2016

@Royalgamer06 I won a giveaway today. My account is currently banned but I entered before the ban. 🙂

psydex commented Apr 14, 2016

Tackyou commented Apr 15, 2016 •

Using this script is not safe. Even if you only use 1 account.

LangoLango commented Apr 15, 2016

I never used auto-solver, but five of my accounts were banned for multi-account. Three left over.

Joaco853 commented May 1, 2016

the mont is eternum

ShoneMakarone commented May 21, 2016

When i want to join a group to complete quests at gleam, i joined and still is message which tell’s me that i’ve not joined. Can someone help me?

RoseTheFlower commented Jun 10, 2016

I started getting this error today after attempting to use Gleam.solver 1.5.3 by Citrinate. I’ve had no issues with it before, taking part in tens of giveaways. As a solution, I just used a different browser and a different Steam account to get the key manually.

Wrascon commented Jun 10, 2016

RoseTheFlower commented Jun 10, 2016

@Wrascon All I can say is that gleam let me have the key despite my twitter account having been used to get keys with my main Steam account. I don’t know if gleam accepts newly made Steam accounts and whether you can join groups using a new Steam account. If you can, I don’t see an issue here.

Wrascon commented Jun 10, 2016 •

@RoseTheFlower, You do not understand. I’m always in such dispensing first step into the main account, I do not feel any problems and throw invite all 7 bots in the group. When it comes to the change of Steam account to Gleam defined it and came to me necessary to change the VPN, because «too many entry». But this is another message is not something that in a subject, and it takes only 3 of my accounts Steam. The rest is just the same message, which is not correct, I do not know how, but in my case the browser definitely not.
Yes, I used to bother absolutely on each account. First included in Steam, Twitter, Facebook and even one account, was doing all the actions and has also made a second account. There is no problem, but then no protection from multi-accounts did not exist.
Now I just have to screw up accounts and can not farm at all 7 to collect the cards on the level of 4.5 or collecting keys for exchanging missed me distribution

dylan-conlin commented Sep 25, 2016

Any ideas how Gleam was able to detect this bot?

dashanlinxi commented May 4, 2022

对于不使用VPN就无法登录网址的用户来说，你们这个公平吗？ 账户滥用应该是那些通过手段注册多个账户的人 而不是这些无辜的人

Footer

© 2022 GitHub, Inc.

You can’t perform that action at this time.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.

Generic error, «We’re sorry but something went wrong» #1340

Comments

CreepySC commented Aug 3, 2018

I’ve tried to deploy Errbit to Azure, but on logon I get a generic error reading «we’re sorry, but something went wrong».
The browser consle doesn’t return any errors, and the Live HTTP Traffic Chart isn’t showing any 4xx or 5xx errors either.
I’ll admit I’m not too experienced with Rails deployment, so is there anything that might stick out as a beginner’s mistake?
Thanks

The text was updated successfully, but these errors were encountered:

stevecrozz commented Aug 3, 2018

It sounds like an error from Errbit. See if you can find the application logs. The info we’ll need to investigate should be there.

Footer

© 2022 GitHub, Inc.

You can’t perform that action at this time.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.

I can’t send messages to supergroups #1208

Comments

mstrey commented Aug 13, 2016

I can’t send nothing to a supergroup. The admins group said me they don’t banned my user, but the message I receive when try to send something is that:
«One of the params is missing or invalid»
Details:
«Method: messages.sendMessage
Url: N/A
Result: <"_":"rpc_error","error_code":400,"error_message":"USER_BANNED_IN_CHANNEL">
Stack: Error
at Object.h as invokeApi
at Z.l.send (https://web.telegram.org/js/app.js:29:5996)
at n (https://web.telegram.org/js/app.js:2:17056)»

What I need to do? How to back this to normal?

The text was updated successfully, but these errors were encountered:

Dwebble commented Aug 13, 2016

I can’t send anything in supergroups (Telegram) too a three days ago. And my friends also have this problema. What should we do? My username is Dwebble, and these supergroups are: https://telegram.me/PokemonRS and https://telegram.me/PokemonSC

stek29 commented Aug 16, 2016

Try contacting @SpamBot
Looks like you’re blocked.

mstrey commented Aug 16, 2016

@stek29 tks for this tip.

I have no ideia why I was reported and who do this. The @SpamBot said me the limitations will be lifted from my account on 19 Aug 20:26 UTC.

I hope who got this prank to me dont do it again.

stek29 commented Aug 16, 2016 •

Well, sometimes sh it happens 🙂
Anyway, it’s not related to webogram, so this issue can be closed, right?

• ← We love you arsenal
• We re sorry this download is no longer available →