sz13
Members-
Posts
16 -
Joined
-
Last visited
Recent Profile Visitors
1,238 profile views
sz13's Achievements
-
Sorry for the delay. I have set up the new 6-month subscription, so the 1-month subscription is ready to be canceled. I assume the VPN information will remain the same, correct? Thanks, as always, for your help!
-
Thank you!
-
sz13 started following [Solved] Ruby ActionCable and Websockets and [Solved] Upgrade VPS98 to 6-month plan
-
I would like to upgrade my plan to the 6-month plan. I believe I am VPS98 (sigmazero13) Thanks in advance! Please let me know if you need anything else.
-
Thanks for the reply. This particular app is a short-term one, but I think the signs keep telling me a VPS may be the better option for this, so I think I'll go that route! I appreciate your help!
-
I am trying to run a Ruby on Rails application that uses websockets via ActionCable. On my local machine (which I used for testing it out) the code itself works fine, but when I uploaded it to Heliohost, the websockets part doesn't seem to be working. I get this error message in the browser console: cable.js:18 WebSocket connection to 'wss://sigma013.heliohost.org/cable' failed: Sadly, it's not giving much more detail than that. Reading through another thread (https://helionet.org/index/topic/29870-java-websocket-on-tommy-default-ports-debugging-general-help/) it looks like it may be something that I can try to get working via an `.htaccess` file in my `public_html` folder, but so far my attempts have not worked. Here's what I have so far (in `/public_html/.htaccess`) RewriteEngine on RewriteCond %{HTTP_HOST} ^sigma013\.heliohost\.org$ [OR] RewriteCond %{HTTP_HOST} ^www\.sigma013\.heliohost\.org$ RewriteRule ^cable\/(.*) "ws\:\/\/127\.0\.0\.1\:8080\/cable" [P,L] RewriteRule ^cable\/(.*) "wss\:\/\/127\.0\.0\.1\:443\/cable" [P,L] I modified the configuration found in the thread to match the path of that ActionCable is apparently trying to use (IE, instead of "sockets" I have "cable"), but I'm not sure what else I may be overlooking. I'm still trying to wrap my brain around what should be in the .htaccess file. I wondered if it's related to the secure socket (using .wss), but if I try the configure my app to use "ws://" instead, it gives me an error saying that you cannot create an insecure websocket from a secure webpage (since the main page itself is using https). I'm hoping whatever change is needed is relatively small, and that I'm just overlooking something with the patterns or something, but any help or inisight provided woudl be greatly appreciated!
-
[Solved] Ruby - Bundle Install failure ("yaml.h" missing?)
sz13 posted a topic in Escalated Requests
Running "bundle install" for my Ruby on Rails project (using the button on the Rails App page in Plesk), and after running awhile, I eventually get the following error: ... Gem::Ext::BuildError: ERROR: Failed to build gem native extension. current directory: /home/sigma013.heliohost.org/vendor/bundle/ruby/3.2.0/gems/psych-5.1.2/ext/psych /opt/plesk/ruby/3.2.2/bin/ruby extconf.rb checking for yaml.h... no yaml.h not found *** extconf.rb failed *** Could not create Makefile due to some reason, probably lack of necessary libraries and/or headers. Check the mkmf.log file for more details. You may need configuration options. Provided configuration options: --with-opt-dir --without-opt-dir --with-opt-include --without-opt-include=${opt-dir}/include --with-opt-lib --without-opt-lib=${opt-dir}/lib64 --with-make-prog --without-make-prog --srcdir=. --curdir --ruby=/opt/plesk/ruby/3.2.2/bin/$(RUBY_BASE_NAME) --with-libyaml-source-dir --without-libyaml-source-dir --with-yaml-0.1-dir --without-yaml-0.1-dir --with-yaml-0.1-include --without-yaml-0.1-include=${yaml-0.1-dir}/include --with-yaml-0.1-lib --without-yaml-0.1-lib=${yaml-0.1-dir}/lib64 --with-yaml-0.1-config --without-yaml-0.1-config --with-pkg-config --without-pkg-config --with-libyaml-dir --without-libyaml-dir --with-libyaml-include --without-libyaml-include=${libyaml-dir}/include --with-libyaml-lib --without-libyaml-lib=${libyaml-dir}/lib64 To see why this extension failed to compile, please check the mkmf.log which can be found here: /home/sigma013.heliohost.org/vendor/bundle/ruby/3.2.0/extensions/x86_64-linux/3.2.0-static/psych-5.1.2/mkmf.log extconf failed, exit code 1 Gem files will remain installed in /home/sigma013.heliohost.org/vendor/bundle/ruby/3.2.0/gems/psych-5.1.2 for inspection. Results logged to /home/sigma013.heliohost.org/vendor/bundle/ruby/3.2.0/extensions/x86_64-linux/3.2.0-static/psych-5.1.2/gem_make.out /opt/plesk/ruby/3.2.2/lib64/ruby/3.2.0/rubygems/ext/builder.rb:119:in `run' /opt/plesk/ruby/3.2.2/lib64/ruby/3.2.0/rubygems/ext/ext_conf_builder.rb:27:in `build' /opt/plesk/ruby/3.2.2/lib64/ruby/3.2.0/rubygems/ext/builder.rb:187:in `build_extension' /opt/plesk/ruby/3.2.2/lib64/ruby/3.2.0/rubygems/ext/builder.rb:221:in `block in build_extensions' /opt/plesk/ruby/3.2.2/lib64/ruby/3.2.0/rubygems/ext/builder.rb:218:in `each' /opt/plesk/ruby/3.2.2/lib64/ruby/3.2.0/rubygems/ext/builder.rb:218:in `build_extensions' /opt/plesk/ruby/3.2.2/lib64/ruby/3.2.0/rubygems/installer.rb:843:in `build_extensions' /home/sigma013.heliohost.org/vendor/bundle/ruby/3.2.0/gems/bundler-2.5.6/lib/bundler/rubygems_gem_installer.rb:76:in `build_extensions' /home/sigma013.heliohost.org/vendor/bundle/ruby/3.2.0/gems/bundler-2.5.6/lib/bundler/rubygems_gem_installer.rb:28:in `install' /home/sigma013.heliohost.org/vendor/bundle/ruby/3.2.0/gems/bundler-2.5.6/lib/bundler/source/rubygems.rb:205:in `install' /home/sigma013.heliohost.org/vendor/bundle/ruby/3.2.0/gems/bundler-2.5.6/lib/bundler/installer/gem_installer.rb:54:in `install' /home/sigma013.heliohost.org/vendor/bundle/ruby/3.2.0/gems/bundler-2.5.6/lib/bundler/installer/gem_installer.rb:16:in `install_from_spec' /home/sigma013.heliohost.org/vendor/bundle/ruby/3.2.0/gems/bundler-2.5.6/lib/bundler/installer/parallel_installer.rb:132:in `do_install' /home/sigma013.heliohost.org/vendor/bundle/ruby/3.2.0/gems/bundler-2.5.6/lib/bundler/installer/parallel_installer.rb:123:in `block in worker_pool' /home/sigma013.heliohost.org/vendor/bundle/ruby/3.2.0/gems/bundler-2.5.6/lib/bundler/worker.rb:62:in `apply_func' /home/sigma013.heliohost.org/vendor/bundle/ruby/3.2.0/gems/bundler-2.5.6/lib/bundler/worker.rb:57:in `block in process_queue' /home/sigma013.heliohost.org/vendor/bundle/ruby/3.2.0/gems/bundler-2.5.6/lib/bundler/worker.rb:54:in `loop' /home/sigma013.heliohost.org/vendor/bundle/ruby/3.2.0/gems/bundler-2.5.6/lib/bundler/worker.rb:54:in `process_queue' /home/sigma013.heliohost.org/vendor/bundle/ruby/3.2.0/gems/bundler-2.5.6/lib/bundler/worker.rb:90:in `block (2 levels) in create_threads' An error occurred while installing psych (5.1.2), and Bundler cannot continue. In Gemfile: debug was resolved to 1.9.1, which depends on irb was resolved to 1.12.0, which depends on rdoc was resolved to 6.6.2, which depends on psych ERROR:__main__:Command '['/usr/local/psa/admin/sbin/filemng', 'sigma013', 'exec', '/home/sigma013.heliohost.org/', '/bin/bash', '-l', '-c', 'bundle install --path vendor/bundle']' returned non-zero exit status 5. Is there anything I need to do to have `yaml.h` installed? This particular ruby app is pretty much using the default rails setup, and the `psych` gem seems to be part of it. Thanks in advance! My subdomain is `sigma013` on Tommy -
Thanks, Krydos! I appreciate your quick help!
-
I should note that in the past, to log into tommy I had to use the "tommy.heliohost.org:2083" URL, though that still seems to be the cPanel login. I'm hoping the new account using Plesk will still have access to some of the features I was enjoying on Tommy, such as Nodejs support (though I know you've said not every old feature is available yet, so if it's not, I can definitely be patient).
-
I just had my account moved to use Plesk, but when I tried logging in, it says my username or password is invalid. I'm pretty sure I have the right username (sigma013) but I'm guessing the password I was using to log into cPanel on Tommy is not working anymore. Is there any way I could have my password reset? Thanks! Scott Lewis
-
Sounds good, and makes sense. Thanks again for your help and quick reply!
-
Thanks, that seemed to work. May be a separate issue then. When I go to "tommy.heliohost.org:2083", I can log in from there with my newly-reset password. However, if I go to "heliohost.org", and use my username/password there, I keep getting the "invalid login" error. I could have sworn I used to be able to log in from there and then go to my cPanel. However, I was recently cleaning up my bookmarks and may have been using a different URL before. I will bookmark the tommy one for now, though,
-
I forgot to log in within 30 days (I had a reminder set, but i must have expired in my calendar). I got the email about it, and tried to log in but the password didn't work, and even after resetting the password it still gives me the "Invalid Login" message. username: sigma013 server: tommy (I think) domain: sigma013.heliohost.org
-
Hmm, strange. I was able to get it to work on a different machine. I'll have to look and see what's going on with the first one I tried, but it's obviously a problem on my end. Thanks! I think I'm all set!
-
128.138.64.220 I can log into the cpanel, but getting the "Too many authentication failures" error from FileZilla. Thanks!